Table layout for items on a pallet

[aas4mis]

I've been out of the access game for a while and was curious what the best table/relationship layout would be for keeping track of items on pallets.

I've got a manifest consisting of name, store, order, and tracking number. I would like to be able to scan a 'start' barcode, scan multiple tracking numbers to a pallet, then scan an end barcode. All items should then associate to a pallet via the unique tracking number so I can later print an end cap to attatch to the pallet before it's shrink wrapped.

Any suggestions on this fairly simple table/relationship layout would be appreciated.

Thanks!

[aas4mis]

With this database being so small it might make sense to use a natural PK based off of the tracking number, but I'd like to avoid that (preference). Please suggest a layout which implements surrogate PK's.

Thanks!

[nico5038]

Obviously using an autonumber with +1 increment is the fastest way, but what about recording the barcode and a date/time stamp ?

Nic;o)

[aas4mis]

I can work out the forms details later (barcode start/stop), I'm just looking for a good base to start with. An ERD if you will. All the manifest info will be imported into 1 table and Pallet info to another table. Not sure the best way to relate the two and what fields to use in the pallet table. I'm sure I'm oversimplifying , should there be a join table? So many ways to organize such simple thoughts, looking for some insight.

[aas4mis]

As much as I want to avoid it I decided to use a natural key based on the tracking number. After a little thought I realized business rules would not always have the manifest data available before the tracking number would be available, breaking my surrogate key design that I had hoped for.