Javier - 1) The db is huge.
2) RBase created another table with exactly the same name as the one I was changing the next autonum value on. It also appeared in SYS_TABLES as another row with the same SYS_TABLE_NAME. This is supposed to be impossible, but it happened. This caused RBase to issue a duplicate table error message for any operation I attempted involving that table in the Object Manager. 3) When I unloaded the table in question into a file only one table definition was written into that file. 4) I used the UNLOAD and recreate method to rebuild the database. The table was defined only once in the structure even though it appeared twice in the table list displayed in the Object Manager and in two rows in SYS_TABLES. Bernie At 03:28 PM 2/24/2004 -0600, you wrote: >Bernie: >Been there, done that. Hopefully you backed up the database prior to >modifying the structure. Does the "duplicate" table have some random numbers >as the name? If this is the case, it is the temporary table that R:base was >using, and it is a pain in the *** to get rid of. The only way that I found >is to: > >If your database is small: >OUTPUT my_db; UNLOAD ALL; OUTPUT SCREEN > >If your database is large: >OUTPUT my_struct.bu; UNLOAD STRUCTURE; OUTPUT SCREEN >OUTPUT my_data.bu; UNLOAD DATA; OUTPUT SCREEN > >Then you edit the structure file, delete the temporary table and recreate >the database. >Javier, > >Javier Valencia, PE >President >Valencia Technology Group, L.L.C. >14315 S. Twilight Ln, Suite #14 >Olathe, Kansas 66062-4578 >Office (913)829-0888 >Fax (913)649-2904 >Cell (913)915-3137 >================================================ >Attention: >The information contained in this message and or attachments is intended >only for the person or entity to which it is addressed and may contain >confidential and/or privileged material. Any review, retransmission, >dissemination or other use of, or taking of any action in reliance upon, >this information by persons or entities other than the intended recipient >is prohibited. If you received this in error, please contact the sender and >delete the material from all system and destroy all copies. >====================================================== > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Bernie >Corrigan >Sent: Tuesday, February 24, 2004 3:17 PM >To: RBASE-L Mailing List >Subject: [RBASE-L] - RE: Edit SYS_TABLES > >Larry and Javier - > > Thanks. I was afraid of that. What happened >was: I was using the object manager to change an >autonumber value and the table name, etc., was perfectly >duplicated by the object manager which then crashed. > > So any changes I want to make are foreclosed >by RBase not allowing any changes because of the >duplicate table. The other strange thing I ran across >was that a table can't be dropped if it has a foreign >key which refers to another table. > >Bernie > > > >At 03:57 PM 2/24/2004 -0500, you wrote: >><< >>Is there any way to edit SYS_TABLES in RBW 6.5++ ? >>>> >> >>No, I believe R:Base is doing a little magic behind the scenes to make >>you believe that there is such an beast as SYS_TABLEs -- in fact I don't >>think it's there. >>-- >>Larry >> >> > >
