This little feature can be very useful, especially when trying to preserve previously/externally assigned ID values.
(But you already know that.) FWIW, if it helps anyone, and because I've been going back and forth between my DB "true love", RB, and my current occasional "hook-up", SQL Server, the analogous statements in her dialect, are: --*** Allow use of existing ID values rather than DB-assigned autonum values *** SET IDENTITY_INSERT [MY_TABLE_NAME] on --*** You've got to ... *** INSERT ... Go where you wanna' go ... INTO [MY_TABLE_NAME] ... do what you wanna' do ... --*** With whomever ... *** SET IDENTITY_INSERT [MY_TABLE_NAME] off --*** All due apologies to the Mamas & Papas *** Steve in Memphis From: [email protected] [mailto:[email protected]] On Behalf Of Javier Valencia Sent: Wednesday, March 23, 2011 11:21pm 23:21 To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Rbase ODBC table Bob, >>> I cannot simply use an autonum column by itself, or doing a data reload would reassign numbers. <<< This is not necessarily true. From the help file: NUM NONUM NUM specifies that autonumbering columns will be numbered as they are loaded. NONUM turns off autonumbering while loading, thereby allowing loading of a specific value for autonumber columns. The default is NUM. As you can see, you can always load your own number into the auto-number column. Javier, Javier Valencia, PE 913-829-0888 Office 913-915-3137 Cell 913-649-2904 Fax [email protected] <mailto:[email protected]> ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Bob Thompson Sent: Wednesday, March 23, 2011 9:26 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Rbase ODBC table Jim, The autonum is a unique index. It is the updating of the Serial # column that gets duplicated. I cannot simply use an autonum column by itself, or doing a data reload would reassign numbers. So the insert command creates a new record. The autonum column creates the "sequential" number. This number then gets updated to the Serial# column for permanent keeping. What is happening is that the ODBC table sometimes gets corrupted or the update results in two serial# values being the same. The autonum does not duplicate. Per Razzaks suggestion, I need to get the last update Thanks Bob Thompson LaPorte, IN 219-363-7441 Sent from my iPod On Mar 23, 2011, at 2:08 PM, James Bentley <[email protected]> wrote: Bob, What is the precise definition of you autonumber column? For it to work properly it must be defined NOT NULL with a PRIMARY KEY or a UNIQUE INDEX as one of the last two items prevents duplicates from occurring. Jim Bentley American Celiac Society [email protected] tel: 1-504-737-3293 From: "[email protected]" <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Wed, March 23, 2011 11:28:52 AM Subject: [RBASE-L] - Re: Rbase ODBC table Thank you for the information on updating and ODBC. -Bob ----- Original Message ----- From: "A. Razzak Memon" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Wednesday, March 23, 2011 9:43:29 AM Subject: [RBASE-L] - Re: Rbase ODBC table At 09:57 AM 3/23/2011, Bob Thompson <[email protected]> wrote: >So my questions are: > >1) When installing Rbase upgrades, does the ODBC driver automatically get > updated as well? I am assuming it does. > > (All users are Terminal Service thin clients, so only one computer is > actually involved. I do not have to worry that one PC did not get > updated while others did, i.e. mismatched versions.) Bob, FWIW, the following files are updated/installed when using R:BASE Updates (especially Turbo V-8) in your case: . RBEngine8.DLL -- Turbo V-8 Core Engine DLL . RStyle8.DLL -- Turbo V-8 R:Style Utility DLL . RB80_64.DLL -- Turbo V-8 ODBC Driver . RB80_INS.DLL -- Turbo V-8 ODBC Configuration . RBG8.EXE -- Turbo V-8 Main Executable . RBG8EE.EXE -- Turbo V-8 Main Executable (Enterprise Edition, if applicable) Just curious ... What exact Update and Build of R:BASE Turbo V-8 are you using? *** 8.021.30820 Is that a CURRENT Update and Build? ****No If not, is there a particular reason why? *****Various Are you using Oterro 8.0? ****Not in this application. If yes, what exact version and build of Oterro 8.0? Please note that "Update 25" and "Build: 8.0.25.30119" is the currently available version of R:BASE Turbo V-8 released on January 19, 2011. R:BASE Updates: http://www.rupdates.com Also, be advised that there will be no support or further development of R:BASE 7.6 & Turbo V-8 after October 2011. Both products have been announced and posted with End of Support (EOS) and End of Life (EOL). Product Comparison: http://www.rbase.com/rbg91/compare.php Very Best R:egards, Razzak.
