> > 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!
I think VB only supports automation-enabled COM items (a couple of my own creations, which have dual interfaces, work just fine), so I'm guessing this DLL doesn't support automation, only the other type of interface (I'm not sure exactly what I'm talking about here, but it's something about the dual interface thing - this DLL probably isn't dual interface). -- Jason Teagle [EMAIL PROTECTED] _______________________________________________ msvc mailing list [email protected] See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.
