>>>>Hello
>>>>
>>>>Within our system we have a VFP exe and a VB exe which share a common object. We create a reference to this object using the CREATEOBJECT() command.
>>>>
>>>>We have encountered the scenario where an error has occurred in VB which has resulted in the object being 'killed'. When we subsequently attempt to reference the object in VFP we get an OLE error - RPC server is not available.
>>>>
>>>>Is there any way of determing whether an object is OK prior to using it's properties or methods?
>>>
>>>Basically, it's error trapping issue. Also, you can check TYPE("oApp.oMyobject") any time before you use it, but I guess it will not give 100% reliable responce.
>>>
>>>It's actually within the error handler that we are encountering the problem. If the object doen't exist then I can bypass some code and terminate the application cleanly. I've tried the TYPE() command but it comes back with a value of O whether the object exists or not.
>
>Could you also check for: TYPE("oMyobject")"O" OR ISNULL(oMyobject)? Also, not that you may trap any error and still terminate the application.
>
> I've tried the ISNULL() and that also returns the same value regardless of whether the object exists or not. Because the error occurs referencing the 'dead' object within the error handler the standard VFP error is displayed which is confusing the users and not terminating cleanly.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only