If I understand correctly, you need to propagate the change, from the main table, to other tables. This is easily done through referential integrity, by specifying the "Cascade" option.

I personally prefer using key fields (primary keys / foreign keys) which the user never sees - but it might be difficult to change an existing system.

>For instance,
>
>ALF-1234-ABC-AM/UL => ALF-1234-ABC-AU
>
>Shorten the item# by /UL => U for UL lamp std.
>....
>etc.
>
>
>The problem is the current Item# in Item table change,
>it will fail to print Invoice and Packing list....
>
>Current way to do:
>
>Make a "ItemMap" table for mapping:
>OrgItem, Item, MapDate ....
>
>and Add a new field: InvItem at OrdItems
>
>if found the Item# exist at ItemMap OrgItem..
>Move the Old Item# to InvItem.
>and Put the New Item# to OrdItems.Item field to re-build the link!
>
>Then, at Invoice Report check out InvItem empty or not to print...
>Because Invoice/Packing Print out need to remain Orginial Item# as
>Proforma Invoice...
>
>
>Accuarately, I think it's still got problem on linking...
>should I make a individual temp dbf after each proforma print...
>then call the small DBF to do remain invoice, packing list task!?
>
>Both way already out of database concept! /._.\