Hi Steve, Thanks very much for taking the time to provide your detailed reply. While I haven't used that approach this time I will note that in case I have similar issues in the future.
As mentioned in my reply to Buddy, I have since fixed this using an older version of the db. I unloaded the tables that had changed in the db with the error, deleted them from the old db and then loaded them from the unloaded .tbl files. Fortunately I hadn't made any other changes to forms or reports. So far it seems that things are back to 'normal'. Thank you. Regards John Docherty On Sunday, November 16, 2025 at 10:35:01 AM UTC+13 Steve Sweeney wrote: > John, > > > > I had a similar corruption – the SYS_COMPUTED column had lost its index: > > > > Examining table SYS_COMPUTED > > Foreign Key: > _dest > > > ------------------------------ > > -ERROR- A column's index file reference is invalid. (1239) > > -ERROR- Error reading the index list. (1222) > > Column: SYS_COLUMN_ID > > Column: SYS_DATA_TYPE > > Column: SYS_PCODE > > Column: SYS_COLUMN_LIST > > Column: SYS_ALGEBRA_DATA > > > > The AutoChk report should have looked like this: > > > > Examining table SYS_COMPUTED > > Index: 5 > > Column: SYS_COLUMN_ID > > Column: SYS_DATA_TYPE > > Column: SYS_PCODE > > Column: SYS_COLUMN_LIST > > Column: SYS_ALGEBRA_DATA > > > > This is an error in the RX1 file. There is probably a way to repair that > error with R:Scope, but I was not quite sure the best procedure to use. If > that works for you the solution would be the fastest way to correct that > error. I tried a different tact, which ultimately worked. > > > > The problem database was on a Thursday morning, but the last good backup > we had was from Monday afternoon. It was entirely too much work to > recreate a company database with thousands of transactions. > > > > The good news is there was no RELOAD or PACK command – AND – there were no > new tables added to, or removed from, the database in that three day > period. That provided an opportunity to use the RX1 file from the Monday > database, melded with the RX2, RX3 and RX4 files from the Thursday > database. The RX1 file would still point to the FIRST record in each of > the 400 tables of this 6GB RX2 file, so the starting point would be > correct. The “Number of Rows” and “Last Pointer Location” would be wrong, > but at least it was worth the try to do a RELOAD command. > > > > I copied the 4 RX files to a different folder for backup, then did a > RELOAD routine. It seemed to work, with the only errors being number of > rows and last location, but there was still an issue with the database that > I could not identify. During the RELOAD there were errors showing up while > the RELOAD was working on the RX2 file, so we needed to try another > solution. > > > > Then, using another copy of the same database I did a PACK command > instead. Interestingly, there were no errors during the PACK command as it > focused on reloading the RX2 file first, before starting on the indexes in > the RX3 file. That seemed to work cleaner. > > > > Finally, using the PACK’ed database I did a RELOAD – it worked flawlessly. > > > > Problem solved – all records were found. > > > > Hope this helps. > > > > Steve Sweeney > > 925-876-3100 <(925)%20876-3100> > > > > > > > > > > > > > > *From:* 'Buddy Walker' via RBASE-L <[email protected]> > *Sent:* Saturday, November 15, 2025 11:49 AM > *To:* [email protected] > *Subject:* Re: [RBASE-L] - SYS_COMMENT_ID is an undefined table > > > > It appears there is corruption in the database. I would suggest make a > copy of the database files. Make sure everyone is out of the database then > try a reload. > > > > > > Sent from my iPhone > > > > On Nov 15, 2025, at 2:43 PM, [email protected] <[email protected]> > wrote: > > I have this error message in a db. I was just wondering if there is any > way of fixing this ? Any suggestions would be welcome. > > > > Thank you. > > Regards > > John Docherty > > -- > For group guidelines, visit > http://www.rbase.com/support/usersgroup_guidelines.php > --- > You received this message because you are subscribed to the Google Groups > "RBASE-L" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/rbase-l/9af1123c-d7ec-4647-a811-4962d7cbb3e6n%40googlegroups.com > > <https://groups.google.com/d/msgid/rbase-l/9af1123c-d7ec-4647-a811-4962d7cbb3e6n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > For group guidelines, visit > http://www.rbase.com/support/usersgroup_guidelines.php > --- > You received this message because you are subscribed to the Google Groups > "RBASE-L" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > > To view this discussion visit > https://groups.google.com/d/msgid/rbase-l/6D4DD7AE-3C0E-4692-ABBC-8540743081C7%40comcast.net > > <https://groups.google.com/d/msgid/rbase-l/6D4DD7AE-3C0E-4692-ABBC-8540743081C7%40comcast.net?utm_medium=email&utm_source=footer> > . > -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/rbase-l/c95cb75a-b517-4937-ab86-78634b765445n%40googlegroups.com.
