On Apr 7, 2006, at 2:03 pm, William Yu wrote:
On 4/7/06 11:58 AM, "GregO" <[EMAIL PROTECTED]> wrote:
So trying to answer my own question, I followed the constructor
format that an ActiveX Object uses when you bring that in:
Sub Constructor()
#if TargetWin32 then
OLEObject("{941BD791-06C1-4D4D-8F6A-8F685810DD5E}")
#endif
End Sub
and of course I substituted the correct GUID for the type library
(got if from the registry). My new Class' Super is OLEObject, and
I've created an instance on a window. So knowing that just adding the
Reference in VB works, anyone have an idea as to why I'd be getting
an OLEException?
What kind of COM object is this? It must support automation, which
means it
must implement the IDispatch interface. Perhaps you got the wrong
GUID,
what does the OLEException message say about the error?
William,
Here's a copy of the IDL for the DLL. Can you tell me what I'm doing
wrong? Am I correct that this event implements the IUnknown
interface, and that's why it doesn't work?
--------------snip----------------------
// Generated .IDL file by TLB2HTML
// Copyright (c) 2003 by Milos Tosic
// All Rights Reserved
[
uuid({941BD791-06C1-4D4D-8F6A-8F685810DD5E}),
version(1.0),
helpstring("QBSDKEvent 1.0 Type Library")
]
library QBSDKEVENTLib
{
// Forward declare all types
interface IQBEventCallback;
[
odl,
uuid({A3A4E33E-E747-48CF-947B-93FDE67FF72F}),
version(0.0),
helpstring("IQBEventCallback Interface"),
]
interface IQBEventCallback : IUnknown
{
[id(1), helpstring("method inform")]
HRESULT inform( [in] BSTR eventXML );
}
}
--------------snip----------------------
Thank you for your time.
GregO
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
