>I have noticed this error when I have created another object over the COM layer and I do not explicity release it. While it should clean up on it's own when it's owner (VFP) goes out of scope, instead it causes this error.
>
>Example
>
>oObj=CREATEOBJECT("myobject.myobject")
>QUIT
>
>Causes error.
>
>oObj=CREATEOBJECT("myobject.myobject")
>RELEASE oObj
>QUIT
>
>Doesn't cause error.
Well,
My FoxPro throughs me out with the error... it is not just when I 'quit' forxpro that I get the error. I would just type a modi proj and get it, or other things.
Also, Pressing buttons in the class browser kicks us out of VFP just like we did a File Exit...
There is more to this than leaving a reference to a non-existing object while quitting.
BOb
Previous
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