Hi Srdjan

>You can keep packing sizes and batch numbers as separate lookup tables.

I can visualize a lookup table for packing sizes (1 to many, PK to FK), but I almost short-cutted my thoughts for batches and was thinking in terms of a view (on the production items table where the batch number first comes to existence) for batch numbers as they are going to be unique in nature, so is it a better idea to have a PK (and a separate table) for an already unique field value? (production of the same item in the same packing on the same day will also never have the same batch number) Please let me know your views.

>Item can have single id , while packing size and batch no, will be recorded only in movement documents themselves
>(purchase orders, delivery sleeps etc)

okay I get this.

>and consecutively generate item movement tables.
>
>I would keep separate item movement table, where each transaction (document) is recorded in its very basic
>unit of measurement (mililiters or miligrams) as one or more records, simillar to debits and credis in accounting.

I did not get this can you expand for me.

>Then you can calculate item quantity balances in a simillar way you would reach an account balance.
>Starting from some openning qty balance + input - output = qty balance as at certain date.

okay understood

>Stock control is infact simillar to accounting, just that it is not the accounts and values but rather
>items and quantities that you are accounting for.

yes.

>Bid with confidence ;)

thanks :)