Steve in Memphis As an old rbase programer that this days run an accountant company I give just one example why sequence should be contigus. If you run an invocing routine and suddenly Invoice # 1563 is not there you account might ask you where is have you taken it out of the books since you got cashpayment? At least in Sweden that would be very profitable but illegal from a tax point of view. So the problem is a real bussniesproblem. Sometimes what I do due to this autonum problem is what I call a manual autonum, that is to say : set v vmax compute max inv# fro invoice;set vmax to (.vmax +1) before the entryform. But thanks for all tips in the conversation now I can give my oldfashioned solution and maybe start use autonum more Gunnar
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of J. Stephen Wills Sent: den 21 november 2002 16:51 To: [EMAIL PROTECTED] Subject: Re: Auto Number Steve, could I ask a couple of Q's? 1) Are the paper forms (pre-)printed w/sequential ID's? 2) If not, must the AUTONUM'd ID's be contiguous? TIA, Steve in Memphis ----- Original Message ----- From: "Steve Johnson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 20, 2002 1:37 AM Subject: Auto Number > To All: > > I have created a simple application that stores permit data in one > table. Other tables exist as look-up tables to fill in repetitive alpha > data in the input form using numerical codes. The input form has an > autonumber column that generates a sequential id number. On completion of > the last field of the form, pressing the "enter" key obviously brings up a > new blank form with a incremented id number. Works great, especially when > one enters 50 to 100 forms in a single session. The only problem is that > if you entered the form by mistake, the autonumber column increments. Even > though you exit with "discard row" the autonumber remains incremented as > expected. The work around is to remember to exit the last instance of > completing the form with "esc" and "save". Not very elegant, but it works. > Now I am going to guess that it is bad form to bring up a new form without > asking if you want to enter another form each time. I am sure there is a > better way to control autonumber more effectively. And I want to minimize > the additional keystrokes needed on a repetitive basis to prevent instances > of an unwanted incremented autonumber column. Suggestions? > > > Steve > > > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
