Karen, Have you tried doing an unload all on the converted database and recreate it again?
Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, May 02, 2012 3:06 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Constraint troubleshooting? Bill and Kenny: Thanks for the thread so far! In our case, no tables have been altered. The database was clean in 7.6, and when we did the "unload all" it gave us these strange messages in the resulting 9.1 database. The database works, but we'd like these to go away. I was going to do as you suggested and drop all FKs and PKs that relate to these 6 tables and then rebuild, but now I know for sure that I'll need a backup copy of the database and compare row count at the end! Karen In a message dated 5/2/2012 2:58:18 PM Central Daylight Time, [email protected]<mailto:[email protected]> writes: Kenny, I'll reconfirm: all tables with the broken PK's-without-reference were tables that had been altered. The database continued to "work", but performance was sometimes poor. And I am pretty sure that all of the alterations had been done in R:BASE 8.0 Turbo. I do not believe I have ever seen this in 9.1, certainly not in the past 8 to 12 months. Bill On Wed, May 2, 2012 at 2:20 PM, Kenny Camp <[email protected]<mailto:[email protected]>> wrote: I experienced this issue several times recently and in my case it was caused by altering a table. I'm having trouble figuring out why this is happening in order to demonstrate to others, but to avoid the problem, whenever I plan to alter tables I unload structure and data separately, then cut the structure file into two pieces. One to build all the tables and a second to add constraints (and the other stuff below the first create index statement).
