Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Backup, error found too late
Message
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
01183112
Message ID:
01183220
Views:
22
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...
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform