Internal Inconsistency error:

[hunterspot]

I have a history table. It has index on field1 and field2. when i try to insert a record i got an error saying Internal inconsistency error" and it closed down VFP. I am getting this only with one record. while trying to find out where the problem lies, started eliminating one field after the another and left with field1 and field2. i used the same data for these 2 fields when i got this error for the first time. I got the error. i changed the value of both fields and the error is gone. when i change the value of one field the error is back. the insert statement or the table don't like that particular data. the data looks fine and it doesn't give error for any other data.
any idea why this is happening?
Any input/advise is highly appreciated.
Thanks in advance.

 

[TamarGranor]

If the table has indexes, try recreating the indexes. That error sometimes occurs due to index or data corruption.

Tamar

 

[GriffMG]

I had this very same problem on Tuesday.

I *think* it might have been to do with the data itself.
I did the reindex and it didn't help.

So, I added a few blank records, and reindexed again.... and that sorted it!

I think it was cause by a large number of very similar index keys, but I have no evidence to support that besides the anecdotal...

Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

 

[Olaf Doschke]

I added a few blank records, and reindexed again.... and that sorted it!

That's why you better DELETE TAG and then INDEX ON to recreate the index. REINDEX does not do the same job AFAIK.

Bye, Olaf.

 

[GriffMG]

Funnily enough, that was why I was asking about iterating through indexes.




Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

 

[DSummZZZ]

Olaf is right in that REINDEX doesn't always cure it. If you have a corrupt index tag or key in the dbf header, REINDEX indexes uses that corrupt tag or key to recreate the index. The only way to fix that is to create the indexes from scratch.


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm