Gary,

In my opinion the current mechanism of logging errors in MereMortals is very far from the best. We have a desire to re-write it at some point, but postponed it because we have more pressing issues at the moment. If you would be successful in changing it on your own, please post it here for our reference.

Thanks a lot in advance.

>Hello everyone,
>
>Has anyone added the ability to have unusual bizobj errors logged into the event log?
>
>I have several ODBC views that can produce errors from a variety of causes. The MMortals framework simply lets the native foxpro error handler present the error dialog (Connectivity Error: (Cancel, Suspend, Ignore, Help)). The app keeps on executing.
>
>The errors can occur during opentables, or requery() or whenever the platform providing the ODBC data source becomes problematic.
>
>I though having the regular framework error handler write an entry to the event log and then shutdown the application would solve my graceful exit problem and allow me to capture what and where the error occured.
>
>Has anyone modified the bizobj error handler to pass errors up to the main event handler. Currently they are being passed up to ccontainer class where it just lets foxpro handle it.
>
>Thanks,
>
>Gary Pike.