>Under normal circumstances it won't generate duplicate key's, however it can skip keyvalues if you make use of buffering and revert changes.

True. But, say an abnormal circumstance happens, for instance, a customer enters data into a setup table in one system, then to avoid duplicate data entry, copies the table into another system. This happens a lot while customers are setting up my app. They usually have a test systems, a parallel system, and a live system. After the test system is accepted and the client wants to run parallel, they copy setup tables from the test system to the parallel system. When this copy happens, the next ID table is now out of sync and may generate duplicate IDs. Can I code anything to prevent this?
Thanks,
John