At 04/22/2003 04:07 PM, Lemon, Craig wrote:
>OK - take this example ... I had written a COM object to be called from a VB
>client. All was working OK- so I thought anyway. Installed in a production
>environment, and then the developer of the VB client told me that his VB app
>would "do its job" correctly, but not exit, i.e. the .exe would hang around
>after all processing was complete. We tracked it down to being a problem
>with my COM object, i.e. if the COM object was not called from the VB client
>then the VB .exe would exit as expected.
>
>So how do you go about finding this??
Step through the COM object to see what was going on.
Phil Daley < AutoDesk >
http://personal.monad.net/~p_daley
