> If I understant your problem correctly, you should be able to set the 3rd
> part DLL up as a reference in something like VB and then use the reference
> viewer to list the interfaces and associated fucntions.
That was a superb idea... but I guess it isn't my day. If I try to select
either the 3rd-arty DLL itself, or our built EXE, it says in both cases
'can't add reference' (whatever that means?). So I'm stuffed. It MUST expose
some interfaces somewhere!
> Out of interest what is the point of your COM server? Is it simply to
> provide an instance for the 3rd party DLL?
The server is designed to talk to devices in the field, and report back
those results in a consistent manner to clients. Thus, what we built on top
uses callbacks the DLL makes into our code to actually collect that data
form the devices on its behalf, and return the data in a way it can
understand to pass on to clients.
It's an OPC server, if that helps.
> I haven't actually done any COM for a very long time (I miss it
> really), but
> I assume you're using ATL and you should be able to find in the code where
> query interface goes through the supported interfaces, but I
> could be wrong.
I'm afraid that part is buried in the 3rd-party DLL and we don't have source
{:v(
--
Jason Teagle
[EMAIL PROTECTED]
_______________________________________________
msvc mailing list
[email protected]
See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for
subscription changes, and list archive.
