Hi Jos,

Of course I meant off. What we do in some of our applications is to have it on always. Then in case of an error, our error handler suggests to fix the table like I described if the user is the administrator, for other users the tablevalidate is switched off and the system administrator is notified.

>>Sorry, then I don't have any idea. However, you should not set tablevalidate off in your application, only in th process off fixing a table, like this:

>>SET TABLEVALIDATE OFF
>>lSafety=SET('SAFETY')
>>SET SAFETY OFF
>>USE mytable && Table with errors
>>COPY TO newtable WITH CDX && to make a new table WITHOUT errors!
>>USE newtable
>>COPY TO mytable WITH CDX
>>IF lSafety
>>  SET SAFETY ON
>>ENDIF
>>SET TABLEVALIDATE ON

>>Setting tablevalidate on permanently is living dangerously!
>>
>
>I think you meant to write "off permanently" but anyway I disagree that setting it off is a dangerous thing. It all depends on the application.