>>>>>You can't do any screen IO from a VFP Server. You'll need to write the information to the error log.
>>>>
>>>>Thanks for responding Craig.
>>>>
>>>>Actually I am using a MessageBox call and I got it to work with very basic information. It still manages to go back to the VFP message. Now I have to figure out how to get the class to release without returning to the method that called the error.
>>>
>>>
>>>Look at RETURN TO MASTER or maybe QUIT.
>>
>>Thanks again Craig!
>>
>>Been there done that.
>>I tried the xBase legacy 'RETURN TO MASTER'. And QUIT results in the ubiquitous 'Cannot Quit FoxPro' I tried 'ON SHUTDOWN'...nada.
>>
>>I have set up the release procedure to return -1. I am calling this from a Delphi app. Everything works fine except when I raise an exception within the server code.
>>
>>I have an Error Procedure in the class and all it does is go there when there is an error and return to the class that had the error, only to show me the VFP default message. I get my message first then the VFP message. It is nerve racking! All I want is for the error method to return to the calling program a -1 and quit. < heavy sigh >
>
>
>Sounds like you might have an outstanding reference to an object. Can you do something like oObject = .NULL.?

See my message to David. I think that I explain what is going on a litte better.

Thanks,