Yeah, yeah... but if he has a baseline of scanning possible tables, and basic testing, HE would know better the types of corruption he's getting and what to look for... I'm not trying to guess for him. I've been working w/VFP since 3, and Fox since 1987... I've only had 3 instances of file corruption my entire history working with people... The most recent was over 10 years ago and haven't seen any since.


>To really check for corruption is going to be very time consuming. You would need to check each field of each record. Even then, there are things that can happen that you can't tell until you start looking at the data. For example, if the pointer to the FPT file gets out of whack, you may only be able to tell when you retrieve the data.
>
>>I agree, but that would just be something I would have put within the
>>
>>

>>IF llBadFile
>>ELSE
>>  */ if not, then check for other data corruption stuff...
>>ENDIF
>>

>>
>>I was just giving a baseline on how to cycle through... As for the particulars of checking things like bad data, corrupt indexes, etc, the user would probably build off
>>ATAGINFO(), TAG(), KEY(), etc functions for indexes, etc...