I've chimed in on this topic before but appear to be a lonely voice crying out in the wilderness...

If you have a corrupted table that can still be opened, you run the risk of corrupting data further if you just ignore it. Bad tags and record counts won't magically fix themselves so if you don't have some kind of automated repair process and you have tablevalidate turned off, the only way you know you have a problem is when your users report odd application behavior; the seek that fails, the phantom data record that they claim they saved, etc.

--

rk

-----Original Message-----

From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com] On Behalf Of Sytze de Boer

Sent: Thursday, March 15, 2012 3:59 PM

To: profoxtech@leafe.com

Subject: Re: 2 versions sharing same databases, one says it's corrupt, the other fine

Dave

Would you consider it quite safe (preferred even) to validatetable=0 Are there any pitfalls to do so ?

S

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/DF1EEF11E586A64FB54A97F22A8BD0441D50E3A335@ACKBWDDQH1.artfact.local

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.