Hi Dave, I think this may be a first for me as I'm going to respectfully disagree :) with something you wrote; specifically the "it makes multi-user applications completely unworkable " comment. My applications are all deployed in VFP9 only for years now and I've left tablevalidate set to its default value (3). Periodically I get a support request about a corrupted table and it gets fixed in a timely way. I've had way more data corruption issues thanks to MS SMB/SMB2/OpLocks fun than any pain I can attribute to TABLEVALIDATE.
-- rk -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dave Crozier Sent: Friday, March 16, 2012 6:03 AM To: [email protected] Subject: RE: 2 versions sharing same databases, one says it's corrupt, the other fine As Richard says, there SHOULD be no reason to run it and I do set it off in all my apps as it makes multi-user applications completely unworkable. However, if you are getting DBF corruption then you need to find out exactly why and how it is happening. Dave _______________________________________________ Post Messages to: [email protected] 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/DF1EEF11E586A64FB54A97F22A8BD0441D50E3A362@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.
