On Thursday 22 November 2001 10:56 am, Jason Wharton wrote:

> > One mans insanity is another mans glory. I find it rather simple
> > and it works fine in an app I am working on. I needed sequential
> > member number. using a unique key from a gen is fine. But I also
> > needed the sequential. In getting the sequential to work, there
> > appeared to be no need for the gen. key.
>
> Your system will fail under heavy multi-user load, count on it.

No it won't. Sorry but I've done the above and tested heavily and its just
not the big problem that people in this group have made it out to be. If you
were recording real-time data from multiple sources then I could see the
problem occuring but not in an application that is user driven. I've tested
all the types of data creation from my application and the longest it ever
takes is a fraction of a second. So even if 10 users all clicked on Ok at
the same time to create new data, they might have to wait 1 second for it to
complete. So weigh this against the users desire to see an unbroken sequence
of numbers and its a no brainer. Its easy to do, in comprehesive testing it
causes no problems, and it solves a users requirement.

--
Brad Pepers
brad@...