>>>Barbara
>>It really depends on how the application is going to be designed to be used. I am programming all of my keys to be able to be used as distributed databases (remote and/or offline views), where access to a reference key table may not be available. I suppose that eventually, I may start using the windows "CSLID" function to generate the unique keys, if I run into the chance to create a globally distributed program (Please excuse me while I wipe off my chin!)
>>//:^)
>
>Larry, I have a couple of programs that are distributed on multiple sites, and where the data is collected regularly to a central point. We use a 'site key' which is added to the ID from the lookup table. As long as there is a standard mode of distribution for new site keys it works beautifully.
What happens if your lookup table gets corrupted by a disk crash and you have to restore from a backup? How do you know what the "Next" number should be? I am a beliver in the KISS principle. Why go thru the bother of setting up a counter and all the error and duplicate checking and record locking if you have a function that can be implemented with essentially one line of code?