Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Corrupted Indexes
Message
From
10/03/2003 18:54:55
Terry Davis
Enhanced systems consulting
Tennessee, United States
 
 
To
17/02/2003 09:58:31
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00753870
Message ID:
00763999
Views:
15
Jim,
I got side tracked. Back on this issue now.
Question1: In order for me to determine if a table header and/or index is corrupted programatically, I can do the following code in a program:

use table1
set compatible on
nsize1 = reccount()*recsize() + header() + 1
nsize2 = fsize(dbf())
set compatible off
if nsize1 <> nsize2
** this table/index is corrupted, log an error do not replicate
else
** table is good, continue with the replication
endif

Question2: what is the '+ 1' represent in the calculation of nsize1?

Question3: when nsize1 is 1 bit greater than nsize2, what does that indicate? header corruption? Reason I ask is I have a couple of tables in the dbc that has 'nsize1 > nsize2 by 1 bit'. I purchased the Stonefield Toolkit yesterday thinking that I could use it to 'fix' the header/index problems, but when I ran the Repair prg against one of these tables it did not fix it, nsize1 is still 1 bit greater than nsize2. However if I do a copy to table2 with cdx, the new table copy is 'good', nsize1 = nsize2. Problem is the new table looses default values, validation rules, etc.

Your thoughts and ideas would be appreciated.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform