Standard form is to use an error handler that displays friendly info to the user - possibly including error number. Other data can be saved in a file. I've also written one previously that sent eMail to developer pool when an error occurred with tons of information about time, user, current table, current form, etc.

>Hi All,
>
>I've had a nagging problem in the back of my mind for a long time.
>
>How do you guys handle problems like, a file not found on disk, a field not present in a database, a procedure returning .F. cos something's gone wrong - d'you get the idea? What use is it to a user to simply log a message "File not found", "Unexpected value" and then bomb out of the application. Is the answer just to log the error and then exit gracefully? Does anyone have any comments. I'd be interested to share any views.
>
>Regards
>
>Paul Robinshaw