RE: VB6 & DCOM

["Steve Morgan" <steve@xxxxxxx>]

OK.

 

First - your parameters are the wrong way round.

 

The first parameter is the class name (or ProgID) "xyz.class".

 

The second parameter is the server name.

 

Second - yes, the class needs to be known on the local machine. If the server is an VB ActiveX Exe, it's easier if there are VBR and TLB files. These are generated with the Remote Server Files checkbox in the Project Properties. If you have these, use clireg32.exe to register the files on the client.

 

If you don't have these, copy the server .EXE to the client and run it with the /regserver command-line parameter.

 

If the server is an ActiveX DLL, then you must be running a DLL surrogate on the server. This is most likely to be MTS, in which case, use MTS to create a client setup program.

 

Hope that helps, if not, let me know.

 

Cheers,

Steve

-----Original Message-----
From: andy.powell@xxxxxxx [mailto:andy.powell@xxxxxxx]
Sent: 06 February 2001 14:52
To: ukha_d@xxxxxxxSubject: RE: [ukha_d] VB6 & DCOM

I was just starting to 'tinker' with it.. I assumed that I could use

        Set myobject = CreateObject("TheServerTheAppIsOn","xyz.class")

but get (error 463) Class not registered on local machine. So, does this
mean that I can run a little util to register the class or do I have to
install the app on the local machine too - not to run it but to register
the class... if you get my drift

[ You'll need to assume that I didn't write the server and have no access
to the code for it - i.e. I just want to attach to it and get info/give it
out]


A.





"Steve Morgan" <steve@xxxxxxx>
06/02/2001 15:48
Please respond to ukha_d


        To:     <ukha_d@xxxxxxx>
        cc:
        Subject:        RE: [ukha_d] VB6 & DCOM

I do (officially, I'm supposed to be an expert in it!)

Steve
-----Original Message-----
From: andy.powell@xxxxxxx [mailto:andy.powell@xxxxxxx]
Sent: 06 February 2001 14:36
To: ukha_d@xxxxxxxSubject: [ukha_d] VB6 & DCOM

Did I read correctly that someone was using VB and DCOM in here...

A.


*********************** DISCLAIMER **************************
This message is intended only for use by the person
to whom it is addressed. It may contain information
that is privileged and confidential. Its content does
not constitute a formal commitment by Lombard Odier.
If you are not the intended recipient of this message,
kindly notify the sender immediately and destroy this
message. Thank you.
*************************************************************


Yahoo! Groups Sponsor





www.

.com

Yahoo! Groups Sponsor

www.

.com