It's unlikely to go away. I am thinking that it is used internally for the RowCount property.
----- Original Message ----- From: "Emmitt Dove" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[email protected]> Sent: Saturday, February 16, 2008 11:51 PM Subject: [RBASE-L] - Re: Using AUTONUM in an EEP > That makes sense ... I was thinking from the portability / standards > perspective. > > Emmitt Dove > Manager, DairyPak Business Systems > Evergreen Packaging, Inc. > [EMAIL PROTECTED] > [EMAIL PROTECTED] > (203) 643-8022 > > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of MikeB > Sent: Saturday, February 16, 2008 11:22 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Re: Using AUTONUM in an EEP > > I don't think so. The Select has to poll the recordset and I believe (from > feeble mind of course) that the "Compute" "as Rows" is a function that gets > the > rowcount from RB1.. directly. > > I think the Select is appropriate where you want a count with a where > clause, > but just to get a row count, I don't think there is much overhead with > Compute. > > JFSAG > > The time on a 78900 row table using compute is 0 ms > The Time on the same table using Select Count (*) is 47ms > > > ----- Original Message ----- > From: "Emmitt Dove" <[EMAIL PROTECTED]> > To: "RBASE-L Mailing List" <[email protected]> > Sent: Saturday, February 16, 2008 10:30 PM > Subject: [RBASE-L] - Re: Using AUTONUM in an EEP > > >> Wouldn't SELECT COUNT(*) be preferable to COMPUTE? >> >> Emmitt Dove >> Manager, DairyPak Business Systems >> Evergreen Packaging, Inc. >> [EMAIL PROTECTED] >> [EMAIL PROTECTED] >> (203) 643-8022 >> >> -----Original Message----- >> From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of MikeB >> Sent: Saturday, February 16, 2008 4:22 PM >> To: RBASE-L Mailing List >> Subject: [RBASE-L] - Re: Using AUTONUM in an EEP >> >> >> You can autonumber you entries without having an autonumber "IN" the > table. >> >> FI, I have a table DbDefaults with some columns, a couple of which "ARE" >> autonumber columns. The Table in which you want the autonumber displayed, >> have >> a Trigger (I actually have an on Row Entry EEP in mine) that sets a form >> variable to which the datacolumn in the row is referenced, so anyway on > Row >> Entry it goes like this: >> >> SET VAR vaptransid INTEGER = (NEXT(dbdefaults,anaptransid)) >> >> where anaptransid is the column that is autonumbered, but is not in the >> table >> where it is being used. >> >> This wouldn't interfere in any way with your program flow and doesn't >> require >> the use of permissions. >> >> I would guess, since I can't recall the last time anyone asked about the >> NEXT >> function, that it is another of those RBase nuggets that is underused. >> >> The thing is, you can call NEXT at the appropriate time or NOT depending > on >> what you want, and come closer to displaying a sequential number. >> >> Another thing, I am thinking the "Compute ROWS" gives you the rowcount of >> the >> table from RB1 without any mechanism or overhead like Autonumber, if that > is >> >> all you want is the number of rows. >> >> >> ----- Original Message ----- >> From: "Ted Lienhard" <[EMAIL PROTECTED]> >> To: "RBASE-L Mailing List" <[email protected]> >> Sent: Saturday, February 16, 2008 2:59 PM >> Subject: [RBASE-L] - Re: Using AUTONUM in an EEP >> >> >> Thanks Mike and Alastair, >> >> I had wondered about the possibility of using AUTONUM in an EEP, and what >> rights in the Grant/Revoke system were required if it were possible. Your >> answers pointed me in the right direction! >> >> I created a user with ALTER rights on the tables I wanted to renumber the >> AUTONUM columns on. Then, in the eep I changed the user to the one with >> only >> the ALTER rights on just those two tables, performed the AUTONUM...NUM >> functions, and then changed back to the normal user. In one instance I > had >> to >> include a 'PAUSE FOR 1' command, in order to let the 'edit using' access > to >> the >> table have enough time to close its connection. It works like a charm! >> >> I am using the AUTONUM columns to provide a kind of running total of > entries >> in >> a table, with each row being numbered sequentially. It is not an > extremely >> important function, but almost a "window-dressing" nice touch in my >> application. Funny how in the world of "bells and whistles", the client > may >> >> think the whistle is important, while you think the bell is the ticket. I >> try >> to provide both, if possible...even though the 80/20 rule kills you > thereby! >> >> Thanks! >> Ted >> >>>>> MikeB<[EMAIL PROTECTED]> 2/16/2008 4:38 AM >>> >> These are just my rules: >> >> Autonumber really should have no function other than to provide a linking >> mechanism to a slave table. >> >> If you need a numbering scheme that has to be reset to 0 or 1 or have no >> gaps >> in it, then you should devise your own numbering scheme. >> >> Autonumber is good for almost 2 billion, so a less frequent rebuild due to >> deletions probably can be done. >> >> YMMV >> >> ----- Original Message ----- >> From: "Alastair Burr" <[EMAIL PROTECTED]> >> To: "RBASE-L Mailing List" <[email protected]> >> Sent: Saturday, February 16, 2008 4:17 AM >> Subject: [RBASE-L] - Re: Using AUTONUM in an EEP >> >> >> Ted, >> >> I'd guess that AUTONUM counts as changing the structure of your database >> which >> is forbidden from an EEP. >> >> Alternatively, if you have an Owner password set up you need to have that >> permission to change an autonumber. >> >> Regards, >> Alastair. >> >> >> ----- Original Message ----- >> From: Ted Lienhard >> To: RBASE-L Mailing List >> Sent: Friday, February 15, 2008 10:51 PM >> Subject: [RBASE-L] - Using AUTONUM in an EEP >> >> >> I have a form that has a button to delete rows from a table. This leaves >> a >> number missing in the sequential RNUM column that I would like to fix by >> renumbering using AUTONUM. When I include the AUTONUM command in the EEP, > I >> get this error: "Autonum aborted, resource unavailable." My syntax works >> fine >> from the R> prompt. I have tried a CLOSEWINDOW to avoid any possibility > of >> having the table already in use, but that does not stop the error. >> >> Syntax used: autonum RNUM in journal using 1 1 num >> Version: 7.6.3.30214 >> >> Any ideas would be appreciated! >> >> Best Regards, >> Ted >> >> Ted Lienhard CNE NCT >> Golden Valley Consulting >> >> >> > ---------------------------------------------------------------------------- >> -- >> >> >> No virus found in this incoming message. >> Checked by AVG Free Edition. >> Version: 7.5.516 / Virus Database: 269.20.6/1282 - Release Date: >> 15/02/2008 >> 19:08 >> >> >> > ---------------------------------------------------------------------------- >> ---- >> >> >> Thanks Mike and Alastair, >> >> I had wondered about the possibility of using AUTONUM in an EEP, and what >> rights in the Grant/Revoke system were required if it were possible. Your >> answers pointed me in the right direction! >> >> I created a user with ALTER rights on the tables I wanted to renumber the >> AUTONUM columns on. Then, in the eep I changed the user to the one with >> only >> the ALTER rights on just those two tables, performed the AUTONUM...NUM >> functions, and then changed back to the normal user. In one instance I > had >> to >> include a 'PAUSE FOR 1' command, in order to let the 'edit using' access > to >> the >> table have enough time to close its connection. It works like a charm! >> >> I am using the AUTONUM columns to provide a kind of running total of > entries >> in >> a table, with each row being numbered sequentially. It is not an > extremely >> important function, but almost a "window-dressing" nice touch in my >> application. Funny how in the world of "bells and whistles", the client > may >> >> think the whistle is important, while you think the bell is the ticket. I >> try >> to provide both, if possible...even though the 80/20 rule kills you > thereby! >> >> Thanks! >> Ted >> >>>>> MikeB<[EMAIL PROTECTED]> 2/16/2008 4:38 AM >>> >> These are just my rules: >> >> Autonumber really should have no function other than to provide a linking >> mechanism to a slave table. >> >> If you need a numbering scheme that has to be reset to 0 or 1 or have no >> gaps >> in it, then you should devise your own numbering scheme. >> >> Autonumber is good for almost 2 billion, so a less frequent rebuild due to >> deletions probably can be done. >> >> YMMV >> >> ----- Original Message ----- >> From: "Alastair Burr" <[EMAIL PROTECTED]> >> To: "RBASE-L Mailing List" <[email protected]> >> Sent: Saturday, February 16, 2008 4:17 AM >> Subject: [RBASE-L] - Re: Using AUTONUM in an EEP >> >> >> Ted, >> >> I'd guess that AUTONUM counts as changing the structure of your database >> which >> is forbidden from an EEP. >> >> Alternatively, if you have an Owner password set up you need to have that >> permission to change an autonumber. >> >> Regards, >> Alastair. >> >> >> ----- Original Message ----- >> From: Ted Lienhard >> To: RBASE-L Mailing List >> Sent: Friday, February 15, 2008 10:51 PM >> Subject: [RBASE-L] - Using AUTONUM in an EEP >> >> >> I have a form that has a button to delete rows from a table. This leaves >> a >> number missing in the sequential RNUM column that I would like to fix by >> renumbering using AUTONUM. When I include the AUTONUM command in the EEP, > I >> get this error: "Autonum aborted, resource unavailable." My syntax works >> fine >> from the R> prompt. I have tried a CLOSEWINDOW to avoid any possibility > of >> having the table already in use, but that does not stop the error. >> >> Syntax used: autonum RNUM in journal using 1 1 num >> Version: 7.6.3.30214 >> >> Any ideas would be appreciated! >> >> Best Regards, >> Ted >> >> Ted Lienhard CNE NCT >> Golden Valley Consulting >> >> >> > ---------------------------------------------------------------------------- >> -- >> >> >> No virus found in this incoming message. >> Checked by AVG Free Edition. >> Version: 7.5.516 / Virus Database: 269.20.6/1282 - Release Date: >> 15/02/2008 >> 19:08 >> >> >> > > > --- RBASE-L ================================================ TO POST A MESSAGE TO ALL MEMBERS: Send a plain text email to [email protected] (Don't use any of these words as your Subject: INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH, REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP) ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [email protected] In the message SUBJECT, put just one word: INTRO ================================================ TO UNSUBSCRIBE: Send a plain text email to [email protected] In the message SUBJECT, put just one word: UNSUBSCRIBE ================================================ TO SEARCH ARCHIVES: Send a plain text email to [email protected] In the message SUBJECT, put just one word: SEARCH-n (where n is the number of days). In the message body, place any text to search for. ================================================
