DBC internal inconsistency - URGENT 2

[StewartUK]

I was just beginning to rebuild the dbc RI code, using the normal VFP utility, and it came up with an error saying it couldn't access risp.old (to overwrite it).

I found that the file was marked read-only, so I changed that (in Windows Explorer) and clicked retry.

I'm now getting the above error, which won't go away.

I think I'll have to kill vfp from the Task Manager, but I thought I would first see if there are any other suggestions.

Thanks,

Stewart

 

[dgrewe]

There are 2 RISP.* files.

Did you change both of them ?


David W. Grewe Dave

 

[StewartUK]

Oh! I've looked through the whole of the C: and my development drive & can only find the one - risp.old on my development drive.

I'm now more concerned about the effect of killing VFP from the task manager.

Stewart

 

[dgrewe]

Did you open the DBC exclusive?
If Not,
Start start another copy of VFP and open it again.
Then stop the First copy of VFP with the Task Manager.



David W. Grewe Dave

 

[StewartUK]

David,

Thanks for your help.

I had opened it exclusive in order to rebuild the RI procedures.

I decided to end task on VFP. I was able to open the database OK and am now validating it.

Stewart

 

[dgrewe]

Food for thought,
I when into GENDBC and altered the code.
At Start up I added

USE xxx.DBC exclusive
COPY WITH CDX To c:\foxtmp\DBCBAK
use



David W. Grewe Dave

 

[StewartUK]

Ah, yes. That does sound like a good idea.

Stewart

 

[ilyad]

Stewart,

In order to avoid Internal Consistency Error you always have to

OPEN DATABASE myDBC EXCLUSIVE
PACK DATABASE
COMPILE DATABASE

before attempting to compile RI. Make sure to make a backup copy just in case.

On a cheerful note - in VFP9 this error is not so critical anymore and the database can be validated.

In VFP8 the database was corrupted beyond repair.