>>this will not help you much, but just note that in VFP it is better practise for each object to handle it's own errors, or at least trap its errors
>>and communicate with the main error object (created as a custom class)
>
>Really what I'm looking for is a garbage collector to use in a beta version of an app while my customer bangs on it. Just want something to capture the situation to disk and then gracefully exit the app. Then I periodically log in with remote control software and grab those error log files. I have a pretty thorough one from the pre-VFP days but there are undoubtedly dozens of VFP-aware ones floating around out there.

I had made a data driven Error handler. In the Table I had every error number, message & flags to as how serious the error. Plus wether to bypass it or document it. It proved very good.

Tom