I have a COM object that runs correctly in the debugger when using an MS Visual C++ client driver in Windows 98, all return flags are valid (0x00) and no unusual messages are generated in the debug window.
I ran the COM object through the debugger using an MS VB client as a driver program, again in Windows 98. The program runs correctly but I notice the C++ debug window notes a first chance exception is raised during the call to CoUninitialize():
(MSADCE.DLL): 0xC0000005: Access Violation.
Note: the message is issued but the program terminates without throwing an exception.
I found a note in MSDN saying that this message is occasionally raised by CoUninitialiize() and can be "safely ignored." ( WHAT?! )
Finally, when a colleague tested my COM object using a MS VB client on Windows NT, the program crashed and raised a memory read exception 0x0000008
It is required that the COM object should run on Windows NT. Is anyone able to point me in the right direction or give me some ideas?