>Today I discovered something about VFP that perhaps all you know but I didn't.
>
>In our payroll application we encrypt tables (all free tables) with Cryptor. This has proved to be a very reliable and fast process, but this morning something very serious happened at at client. A key table became corrupted two hours before the payroll was due to be sent to bank. 1800 employees. Last backup was yesterday at 4 pm but they kept working till late in the evening.
>
>First thing was to determine if the problem was with the encryption.. The DBF and FPT files could be read with MODI COMM, so that seemed to be ok. Whew! Made unencripted copies of the table for the next step,
>
>Searched Google and the UT finding leads which directed to FoxWiki and from there to a couple of table fixing utilities, but no luck.
>
>Finally I found message 1306603 by Rich Pupko who mentioned the SET TABLEVALIDATE command. Hmmm. Went to VFP help and after a couple of attempts, voila! Just in time! No kidding.
>
>So I am writing to alert everyone to this useful command. I chose SET TABLEVALIDATE TO 8. While the VFP help states that "SET TABLEVALIDATE does not have repair functionality; it performs only integrity checks as specified by nLevel", the fact remains that it allowed the table to be opened and copied, at which time it was saved correctly.
>
>So thank you Rich Pupko, UT and the VFP team itself. You bet I will incorporate this knowledge into the recovery routine for the future.
>
>Alex

Thanks for the kind words.

That's whats so great about the UT. Knowledge is power, but the really powerful people here are more than willing to share.
I've benefited immensely from several people here and am grateful to have had a chance to offer some help in return.