>>I dont think any COM Server is "better suited" For ComReturnError(), but again i maybe wrong!, Let me take the RecordSet Example and turn it into a Dbf example without MTS
>>
>
>PMFJI, I think the moral of this story is that COMReturnError() should not be considered an error handler, but only an error reporting mechanism. I believe that is the intent of this function. IMO, as long as you do appropriate cleanup work in the error handling routine, I don't see the harm in reporting the error through COMReturnError(). This can be useful since the client probably has a built-in routing for displaying the error.

How can you cleanup Objects Created with LOCAL in the method where the error occured ? There is no way you can get back to the method to set them to NULL !