This is the technique I use, however this is a VFP bug, IMHO. I have it happen fairly regularly and I'm not doing extensive DBC changes. Another bug related to the DBC is VFP's ability to corrupt views. A view will get corrupted and one error you'll get will be "can't insert a record into the base table" or some wording similar to that. I've discovered that what causes that is that VFP puts an unneeded table in the Tables property. For instance, if you run GenDBC and look at the code for the corrupted view, you might see TABLEA,TABLEB in the Tables property. However, only TABLEA would be required. More specifically, let's say all editing is going on in TABLEA. TABLEB is only JOINed to bring in a description for a code value (i.e. the TABLEA has a code that represents a STATUS, but you also want to display the DESCRIPTION of the status, so you join to TABLEB and bring in the DESCRIPTION field, but that field is not edited - it is only for reference). In this case, the Tables property should have only TABLEA in it, but VFP puts TABLEA and TABLEB. Running GenDBC, copying the code for the view in question to a program and removing TABLEB from the Tables property and then running the program to recreate the view solves the problem, but you go to all this trouble due to a VFP bug.


>Naomi,
>
>I tried your suggestion of COMPILE DATABASE myDATA followed by PACK and then went into the RI wizard. And it works!!
>
>I had not come across the COMPILE DATABASE syntax before.
>
>Great - many thanks.
>Barry
>
>
>
>
>>What is your VFP version? In VFP8 this error pretty much meant, that you now need to restore from the backup.
>>
>>In VFP9 we were able to recover from this error using VALIDATE DATABASE RECOVER.
>>
>>In any case, before attempting to change RI, always do the following:
>>
>>1. Make a backup
>>
>>2. OPEN DATBASE myDATA EXCLUSIVE
>> COMPILE DATABASE
>> PACK DATABASE
>> re-build RI
>>
>>>After editing referential integrity and trying to save I get the above error message. I have tried VALIDATE DATABASE and I have also deleted the .dcx index file as suggested in the help file and opened up the dbc again when the index is rebuilt, but to no avail. The 3rd Help suggestion ("call Microsoft support") does not fill me with joy.
>>>
>>>And to make matters worse, the only way I can then quit VFP is to shut it down in task manager. Groan.
>>>
>>>Any help greatly appreciated.
>>>
>>>Barry Sutton.