Building an Access 07 DB for logistical needs

[tatmck]

I have to fill a form everytime I ship something and am in the process of building a data base to keep track (i.e. how many widgets have I sent to such and such rig on what date by manifest serial number-this is the key in my table)Pretty straight forward but the problem is that the number of widgets on each manifest change with each manifest. Could someone shed some light on how to normalize this anamoly by using an info entry Form(build a Form button using VB that would add a column for the number of items on a manifest that would never exceed, say 50 items? Maybe duplicate all fields of that manifest serial # in the table for the number of different widgets and their different descriptions?)

[NeoPa]

Normalised data is held in tables, not in forms. Looking at the forms required can only tell you what is required. You need to determine first what is required from your database, then come up with a structure of data that will support that requirement. Consider at each point where the information fits. If there may be multiple items of one sort that relate to another then you probably would not design a single table to store both, but rather have separate tables with a Foreign Key relationship between them reflecting a One-to-Many relationship.

The design of a databse is beyond the scope of a question on here. We do not offer such services, but we can help with specifics if you get stuck. A good place to pick up understanding of this issue is Database Normalisation and Table structures.

Good luck.

[tatmck]

Thanks for the response. I should have clearified that I do have a table built, somewhat. I've been looking at examples, i.e. customer buys multiple items: choose from existing list of items to store what was bought under that name on such and such date. What if I'm recording what was sent but because of the infinite possibility of what can be manifested (from a pen, to chalk, to a server, to 30 top drive parts)I cant choose from a pre-determined list and want to have the freedom to add "item columns" freely (never exceeding 50 columns)to enter info from the form to the table. Maybe I've got it backwards in trying to normalize the random data, but I hope I didn't confuse you.

[NeoPa]

tatmck:
Maybe I've got it backwards in trying to normalize the random data, but I hope I didn't confuse you.

It sounds like it I would say, from the little I know. See the linked article for a better understanding. If you don't get it from that then nothing I say is likely to help you.

I'm not sure I was confused as such. There was so little information of any sort that I don't think that comes into it. Of course, as I mentioned in the earlier post, we don't design databases for you. The most I can do for you without a more specific question I have done (Give some basic tips to lead you on your way).

[tatmck]

Ok, I'll take a look. thanks anyway.