A recent post got me thinking about error reporting.

I do error trapping to prevent data corruption, but haven't implemented error reporting in my solutions. I like the simplicity of Genx's custom dialog. "Note to Developer:... " which can help diagnose problems and gives the user the tools to help the developer.

What are other ways of error reporting that you've used? E-mail on error? Setting a $$log that gets written to an separate table on close? Include Get(ScriptName) and Get(LastError) in the $$log?

I'm thinking out loud here, but don't want to reinvent the wheel so am interested in other's thoughts/practices.

Thanks,

David

I don't log errors like that. It also depends on how "error" is defined.

FMP defines an empty found set after a find as an error ("No records match this request.") In this case, trapping is required to prevent the error message being displayed AND to correctly determine the steps to follow when no records are found. However there is no reason to notify the developer that the "error" occurred because an empty found set might be a valid condition.