Haha...well, if a global error handler was in place, at least the error would be handled and the user wouldn't have experienced a crash...some situations demand that the program gets out to the user by a deadline...and object-specific error handling is not always a priority.

Are you suggesting a global error handler is not be better than sitting back and waiting until the program crashes on the user in those spots where you forgot to program error handling code?

Joe

>>>In my opinion, this is the way to do it...a global error handler should be set-up and this is one of the errors it could handle....
>>>
>>>Joe
>>>
>>>
>>>>Try using an error handler
>>>>
>>>>on error do errhandler()
>>>>
>>>>errhandler()
>>>>
>>>>if error() = 1582
>>>>
>>>>
>>>>endif
>>>>
>>>>
>>>>1582 I think is the error number for a field validation error. You can check in the help contents of Visual Foxpro under the Technical Reference.
>>
>>Excuse me on this, but is this not a non-oop way of handling it?? I would think the form or whatever is doingthe update to the table/column should handle the error as apposed to GLOBAL error handler..
>>
>>Am I wrong here??
>
>
>You're correct. The error should be handled by the object.