Configuration needed to work with DCOM

Hi,

I am trying to use a remote component and I am getting all kinds of errors.

The syntax I am using:

set MyObj = CreateObject("MyDLL.Class","MyServer")

- everything is ok if myServer is the local server
but if myServer is a network computer.. :mad: it doesn't work!

I have run DCOMCNFG and gave permissions to launch and execute... in fact I am admin on both machines to avoid more problems.

I am assuming I need some configuration on the client side...
and i don't know what to do?

I'm getting two error in two different projects...I don't know why
1 - ActiveX can't crate object
2- Lincense information is missing for this component. You don't have the right licence to run this in desing mode .

I have this problem with a Standard exe client and ActiveX exe Server.

WHat if I want to use a C++ dll as a server!!!!!!!!!?????????:eek:

Any help is appreciated!!!!!

Thanks!

couple of things, first off, try registering the component on the server machine using the regsvr32 tool, then change this line (which probably won't make any difference but let's go with it anyway)...

set MyObj = server.CreateObject("MyDLL.Class","MyServer")

hi,
if u have created ActiveX for remote using, i suppose it is ActiveX EXE.
the steps u need for that procedure r:
1. in Component tab at Project Properties check the option Remote Server Files.
2. Compile the project. look in the folder where the files produced for .VBR and .TLB files (with the project name).
these files designate for the clients machines.
3. copy and launch your EXE at the server machine (u don't need regsvr32 for that at all) it will automatically register the server registry, then configure DCOM.
4. copy the .VBR and .TLB files to the client machine and use clireg32.exe (u can find it at Visual Studio\Common\Tools or download it from msdn) to configure the client registry (u should specify the location of the .VBR and .TLB files when u run clireg32).

after that u can (at the client application) use Reference instead of CreateObject function from VB environment.

u can also make it automatically with some installation tool if u like.

hope it will help.