> 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??
The first thing I'd try on this problem was checking the reference
counts using the ATL debug macros.
-------------
Ehsan Akhgari
List Owner: [EMAIL PROTECTED]
[ Email: [EMAIL PROTECTED]; [EMAIL PROTECTED] ]
[ WWW: http://www.beginthread.com/Ehsan ]
"Steps taken forwards, but sleepwalking back again..."
- High hopes, Pink Floyd
