Error Code 53 - BTree record Number Mismatch

[NickBurr]

Hi,

I am having a problem with a paradox 7 table. Every day we have to perform a table repair because the following error appears:

Error Code: 53
Error Level: 2
Description: BTree record Number Mismatch from block (51) record(1) to block(1)

(It appears three times in the errors list??)

The table itself is 8Mb in size with 7 secondary indexes, No security. Reindexed daily

I have spoken to Corel and they said to export all the data to a text file and import it back in without borrowing the structure from any other table, which i did but this did not fix the problem.

If anyone has the same problem, or if an many advice please let me know it will be gratefully received.

cheers

 

[Langley]

Just out of curiosity, is it 'really' a Paradox 7 table or is it a paradox 4 table? Paradox will use the 4 format when it can. That being the case, you might try an alternative table repair utility - like TUtility. I've found that the Table Repair utility in PdoxWin is not completely reliable.

Mac

 

[NickBurr]

Thanks for your reply, I have checked and it is Paradox 7 file Can you tell where i can get a copy of the Tutility program so i can give it a try.

cheers

 

[Langley]

Steve Green has one on his website -

http://www.diamondsg.com/tutility.htm

 

[JoeNg]

If you have recreated the table without using any existing table’s structure etc. I believe the problem is how the table is used. Under what condition did the error occur? During data entry, after data import etc.
Is it on a network or standalone computer? Used by one or multiple users etc.

If you can determine when the problem occurs would narrow down the problem a lot.

 

[NickBurr]

Langley, thanks for the link I will give it a try.

JoeNg, the table is on a Microsoft NT4 server, Networked (TCP/IP) with 15 client machines (95/98) All path settings are using UNC.

The table itself only gets used for data entry and querying, no other functions like data exports or imports happen to this table.

I do think it could be table related more than the way we use the table, because i have got 30+ Customers using the same system in the same way, on the same platform without problem.

Saying that I am willing to Look/Try anything to solve this problem.

cheers

 

[NickBurr]

I have tried using the Tutility table repair utility, and unfortunately it did not work,

Has anyone else got any ideas?