Hello peeps. Long time no post.
I will get straight to the point with my problem. I work for a courier company. I have actually designed a simple enough database for our requirments and have been running it since before christmas. It was my first time designing a database and to be honest I got much of the advice I needed from this forum and other access forums. Since I have been using the database that I designed I have noticed things that I should have entered and also things that I can make better.
Off-field issues talk of Eagles camp - 7/31/08 - Philadelphia News ::
Off-field issues talk of Eagles camp. Advertisement. Thursday, July 31, is focused on football, some of his teammates are dealing with off-field issues.
http://abclocal.go.com/wpvi/story?section=news/sports/pro/football&id=6300187HOME |
Associating Field Behaviour with Issue Types::
allowing administrators to reuse the same field configuration for issue type mappings across the issues in the project use the. Default Field Configuration
http://www.atlassian.com/software/jira/docs/v3.13/issuefield_configuration_schemes.pdfHOME |
One of the things is regarding the reference numbers I have to enter for each job. I only done one field for the reference number as most of the time we are only provided with one. However a couple of our customers provide us with numerous jobs that all have a different reference number. Now the problem is I dont know how to go about setting this up for numerous reference numbers.
I enter each job we do into the database via a form that is obviously from a table. I don't know if can name ONE field Reference Number then when it comes to designing the form can I use the Reference number field three or four times or on the table design do I have to have seperate reference number fields such as Ref No 1. Ref No. 2 Ref. No 3 and so on?????
Issues for Money CCK field | drupal.org::
Home Download Modules Money CCK field. Issues for Money CCK field. Login or register to create an issue · Statistics · Advanced search
http://drupal.org/project/issues/moneyHOME |
Description of issue definition fields::
This field contains the date of the most recent Issue labels update that automatically updates these four fields when you run the Issue labels update.
http://www.cwcsoftware.com/webhelp/Definitions/Description_of_issue_definition_fields.htmHOME |
I hope this makes sense can't think of any other way of describing what I mean. So I hope its clear.
Please could someone give me some pointers on this matter. I am thinking that because the JOB DETAILS table is the largest and main one that the other reference numbers and the not so important details can be entered on a sub report in the tab form style. Is that a good idea???
At the moment in the database I am using now the main table (JOB DETAILS) is huge with over 20 fields which is why I want to seperate the form style into main and sub in the new database that I am beginning to design. So any ideas would be appreciated. and i mean ANY ideas that you think may help me in my cause to better the database design I have at the moment.
One more question. When my new database is completed is there a way of transfering the information from the database I am using now to the new one that I design. They are both access databases????
Thanks for all your help in advance as I know that someone will reply. As I mentioned before I received all the advice I needed to complete my first database from this very forum.
I understand that it is best not to start changing the designs of a database that is in use is this correct?? So I couldn't just change the database I am using now to make it better rather that start designing a brand new one???
Thank you again and I apologise for waffling on.
Bye Bye
Clare
A.K.A Switchwork
If you are going to "re-engineer" a lot of the database, I would suggest reading up on "normalization"
Here is a good link:
http://www.bkent.net/Doc/simple5.htm
the right way to handle an unknown (and presumably endless) number of reference numbers would be to have a secondary table with the JobID as the key (duplicates OK) and then a field to record all Reference Numbers for the JobID then have a subform in the main form (Master/Child fields being JobID) so all the reference numbers that are relevant to the JobID come up.
i have no idea if this will complicate processing your Receipts, Job Tickets, etc. but if it's just a matter of printing Reference Numbers on the one Job Ticket, then the job of changing your code shouldn't be too complicated.
hth,
mac
 I Am a Sinner – What About You?
 Global Sourcing and Supplier Online by Dylan
|
Field issues.