>>Returning .f. from the trigger prevents invalid statuses from being set but >also displays the VFP messagebox 'Trigger Failed'. Not only is this not >visually desireable, I'm sure that it will present problems when the database >is accessed
>
>You should be able to handle this message with an error handler. This is ERROR 1539.
>
>BOb

An ON ERROR solution is fine if the data is being accessed solely by a Fox front-end. How would this be used if the data is being accessed from another client (i.e VB) or if the data is accessed directly using the Command Window? The RETURN .F. from the SP causes the 'Trigger Failed' messagebox to fire. Can you suggest a method of suspending an existing error handler, trapping for error 1539, and re-enabling the prior error handler from within the SP?