Problem with COM object

[Blue Knight]

Hi All,

I was wondering if someone could help me with this problem. I have used
BCB6 to create two separate COM DLL's - the second one uses ADO, but I've
tried it without using ADO as well.

I have successfully registered both DLL's on an NT Server. When I use ASP
on the first COM DLL set obj1 = Server.CreateObject("Com1.Intf1"), it works
fine. However, when I use the second COM DLL set obj2 =
Server.CreateObject("Com2.Intf1"), it fails with an unknown interface
error - 80004002.

I have created a VB5 app on the NT Server and managed to successfully create
an object using the second COM DLL set obj1 = CreateObject("Com2.Intf1").

Has anybody ever come across this problem before?

Regards,

Bevan

[Mark Guerrieri]

80004002 = No such interface supported... make supre you don't have a typo
in the 'Com2.Intf1' - obviously make sure Com2 actually implements Intf1...

Mark

"Blue Knight" <beva...@Xhotmail.com> wrote in message
news:407e...@newsgroups.borland.com...

[Blue Knight]

Hi Mark,

Thanks, but I solved the problem after all. It seems that I had created a
COM object instead of an Automation object (apparently it makes a
difference). Also, when I ran regsvr32 it didn't give Everyone at least
Read access to the TYPELIB entry in the Registry, unlike it did for the
other DLL. I still haven't worked that one out, but I can easily edit the
Registry permissions myself for now. Oddly enough though, I didn't have
that problem when I installed it on a Win2k server!

Thanks for the reply anyway.

Regards,

Bevan

"Mark Guerrieri" <mar...@comcast.net> wrote in message
news:40847abe$1...@newsgroups.borland.com...