Hi John,

I use a unique idnum (c,10) field in every table in an application along with a branch field. At installation time, a unique 3 (001 - 999) character branch number is assigned to the main system file for the application and then all unique idnum's are generated to include the branch prefix eg. 0010000000001.

The reason for standardising on this method is that I have had a number of single sight customers wanting to go multi site at a later stage. This way I can amalgamate any data from any site to the head office without any problems.


Regards
Doug Johnston

>Hi,
> I am developing a multiuser application, POS and inventory.
> This application will be sold to a company which has branches. According to client, head quarter and branches will take care of their own stock, and sales. It is fine since they will not "cross" to other database in different location.
> However, they have a requirement that, headquarter should able to collect all of the data from branches for strategic planning and may be other checking purposes. Therefore, they need to know where do the invoices, PO, and etc being issued.
> How would you design it in order to recognize those records?
>
>Thank you