I've got a problem in one of my products, reporting a error 2065: table "mytable" has a file length /record count inconsistency that will not allow this transaction to be committed.

The table in question is a transaction log table and is involved in other transactions as well. The problem is that it only errors in one certain transaction, while any other transaction still is fine. It really seems like a VFP bug to me, since in both cases there are records appended to "mytable".

Anyways, I saved the contents, zapped the table, and it seemed fine again. However it still is strange that one occasion it errors on END TRANSACTION and in another it does not, while the code within the transaction is very simular, but involving other tables.

But, OK, I can live with the fact that if there is a problem in the table it is going to error. I'll just have to repair it.

However, more serious, I've got the same problem in one occasion where from time to time the problem occurs on a CURSOR (SQL view) rather than on a table (it is refering to a temp table). Since the cursor is made within the same VFP session and stored in a temp file on the local HD and the behaviour has presented on different machines, I highly doubt that this has anything to do with hardware issues, there must be something within VFP itself causing the problem. Unfortunately the behaviour is difficult to reproduce and there certainly is quite a bit going on within the transaction.

BTW SET TABLEVALIDATE is set to 0

Anyone with the same experiences. any hint or trick ?

Walter,