...
The worst hassle are the customer IDs. I had to allow for new customer records to be created independently on each site (they have trouble communicating with the central), just taking care they remain unique, and then had to create a routine for the central site to put those codes together, because same customers may appear at several sites. Now when a temp ID is replaced with a permanent ID, I have to scan for all the records with that customer's ID and replace it for the new one, plus mark these records for distribution, plus keep this temp ID in a separate field in the customer table, because by the moment the ID is updated in the central, there may be new records with this temp ID at outer sites, so they'd have to be updated later when they arrive....
...
This is the problem I envisage - unique ID's are no problem (I use a HUB-ID and append it to each primary key) but the possibility of a record appearing twice and not being automatically 'welded' is worrying: I could only think of 'flagging' the record(s) at one or other site and prompting for human intervention.
=========
Thanks for all the answers: I'll just have to keep searching...or write my own [hair turns grey, hands shake]
Previous
Next
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