Hmm.. never send a copy of a BSTR to a COM method. That means that the method is responsible for cleaning up the string. This however is against COM rules, as [in] parameters MUST be managed by the caller. If the string has to be marshalled through the method call, then the string passed in will be lost (memory leak), and the callee will free a bstr which it does not own (the marshaller owns it). Thus, if you are using a _bstr_t or a CComBSTR, pass the BSTR pointer (or adress of if passing as an [out] argument) managed by these classes. [in] parameters are managed by called [out] parameters are allocated by callee, and passed for ownership to caller -- Ich bin Joachim von Hassel, und ich bin Pilot der Bundeswehr. Welle: Erdball - F104-G Starfighter

Hello Aby, I have some clues as to what might have gine wrong but I need some more information from you first : Is the events proxy code implemented somewhat like the following ? : HRESULT Fire_SampleRecordPkt(VARIANT vBytes) { CComVariant varResult; T* pT = static_cast(this); int nConnectionIndex; CComVariant* pvars = new CComVariant[1]; int nConnections = m_vec.GetSize(); for (nConnectionIndex = 0; nConnectionIndex < nConnections; nConnectionIndex++) { pT->Lock(); CComPtr sp = m_vec.GetAt(nConnectionIndex); pT->Unlock(); IDispatch* pDispatch = reinterpret_cast(sp.p); if (pDispatch != NULL) { VariantClear(&varResult); pvars[0] = &vBytes; // <-- important. DISPPARAMS disp = { pvars, NULL, 1, 0 }; pDispatch->Invoke(0x1, IID_NULL, LOCALE_USER_DEFAULT, DISPATCH_METHOD, &disp, &varResult, NULL, NULL); } } delete[] pvars; return varResult.scode; } Please note the line in which I added the comment "// <-- important.". Please let me know because I suspect your problem may be a case of wrong code generated by the wizard. Please revert, Bio.

There is no reason to do "Set ...". Try to write bytes = pkt.GetBytes With best wishes, Vita

The question arises: are you willing to export an object of the class from the DLL, or the definition of the class ? If it is the first one, then may I suggest that you create a global object inside the DLL's code, and export a function from the DLL which returns the address of this object. This, however, requires that you have the definition of the class available at the loading application in order to use it. I do not know for sure how well you can use C++ header files in a VB project, or if there is a conversion available. -Antti Keskinen ---------------------------------------------- The definition of impossible is strictly dependant on what we think is possible.

Thanks. I did not get any output in the Error Lookup with Embedded VC++ but did get when i used the one with VC++. Thanks again.