General information
Category:
Databases,Tables, Views, Indexing and SQL syntax
Hi John,
I agree with Cindy... When we developed our Inhouse app we also
needed to know where the records originated from, so we used
a field called Location_id.
Anywhere where we would need to seperate them out, we'd need only
to look at that field. On the other side, you could also roll-up
the figures by disreguaring this field...
Good Luck!
Bob
>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
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only