Would you have to limit access to the table to a single user at a time, at least in a multi-user environment? This would be to assure that no 2 users hitting the table simultaneously get the same number, if that's possible, as well as other potential problems related to many users accessing the table. There should be a very small (perhaps not even noticeable) performance penalty, given that, if I understand correctly, there will be only one or at most a few rows in the table, and the user will "hit" it, getting the number, the table will be updated, then the user will "go away" again, until next time.
Just my less-than-2-cents, Steve in Memphis ----- Original Message ----- From: "Lawrence Lustig" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Monday, June 07, 2004 1:45 PM Subject: [RBASE-L] - Consecutive numbering > Usually I just use autonumber columns and don't worry > about missing values (in the event a user deletes a > row). Now I need to write an application that > consecutively numbers records (no gaps in the > sequence). I also have an autonumber field to use as > the PK. > > My inclination is to handle the numbering in an ON > AFERT INSERT trigger, using the NEXT function against > a "dummy" autonumber table to get the value. > > Does anyone have any thoughts or other suggestions on > how to handle this task? > -- > Larry > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com >
