Developer Forum

Hello to all I hope I'm in correct newsgroup...
What is the best way to resolve the following situation:
Let say we have a company with 3 departments. Each of them assign a
unique ID number to its customer. A person may be customer to one
department only or to all of them. If the company decides to give an
end to this mess by assigning a globally unique ID (for all three
depts) what is the best way to do it without miss the old references of
each department to its customer?
My solution seems very simple and I would like your comment on it: Just
start to assign a new ID for the new customers as well as old ones in a
primary key while in other fields stores the old IDs from each
department. That means that there will be three fields for each
department and an additional one for the global ID. So a customer may
have one (if new), two, three, or four (old customer of all
departments) fields. This seems to me very ugly but I can't think
something else.
Could someone help me with this?

"polman" < XXXX@XXXXX.COM > wrote in



I'm not sure what made you think this was the correct newsgroup. I'd
post such a question in comp.database.ms-access or in the microsoft
general Access newsgroup. Your question certainly has zilch to do
with Jet replication.

--
David W. Fenton http://www.yqcomputer.com/
usenet at dfenton dot com http://www.yqcomputer.com/

David thank you for your time and apologies for the inconvenience.