My point is that if you have an error in one of your tables, and SET TABLEVALIDATE TO 0 lets you bypass the error message, you are taking a big risk. There is always a reason for the error, usually a hardware error like a bad network connection or power failure, or someone 'forgets' to shut down Windows normally. I have had situations where SET TABLEVALIDATE TO 3 (default) reported bad tables, and I was able to fix the tables before any real damage occured.


>I agree that if there is a minimal performance hit, it is best to leave SET TABLEVALIDATE on. How do you access your tables and how many users are regularly using them? All of our programs are essentially file-server based, and we probably don't have any more than 50-100 users in a file at any given time.
>
>Thanks for the reply,
>
>Brian Vander Plaats