>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.