>>In fact, the classes that I am using
>>for my application framework handle the errors in the same manner, but
>>don't provide the information the "fpwerror.prg" did...Well, time to roll
>>up the shirt sleeves...
>
>I think the theory here is that fpwerror would return too much information. :-) While I don't know what information fpwerror returned, I'm sure it's all accessible from native Fox calls.

No, not exactly. The idea is that your error handling should be encapsulated in the object that caused the error. I have a general error handler that will capture errors for objects that don't have specific error handling. It isn't elegant, but it does work. For a few objects, I write custom error handling routines for their specific cases.