Thank you Craig,
However, I seem to be in a catch-22 here:
Since I have to issue myObj.Show() to activate (display) the object,
and, since my program execution suspends at that point until
the object is completely destroyed, I can't evaluate a method or
property until AFTER the object has been destroyed which, of course,
generates the error "object does not exist".
Am I doing something bass ackwards?
David
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