Re: DCOM
In your VB code don't use a ProgID, but the object's CLSID
in the form "clsid:xxx". Then you won't need any registry
entries for the CLSID at your client (in theory, I haven't tried
it in practice...)
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================
"hula" <b@n-wt.com> wrote in message
news:1162551096.987581.291100@h54g2000cwb.googlegroups.com...
hula schrieb:
Brian Muth schrieb:
I forgot to mention that i already tryed to register the server-TLB
on
the client, but got the errormessage: Interface not registered in the
vb-app on the client.
I've never heard of getting this error message when trying to register
the
TLB. Are you certain? Or do you mean that _after_ registering the TLB
you
still get the message "Interface Not Registered" when running the
client?
Brian
Yes i get the error message after registering the tlb in the vb-app
You somehow need to register the relevant interfaces and objects on the
client. It could be a dll, an exe, or the TLBs ...
I thought registering the tlb is enough?
Ok i did it this way:
Register the tlib on the client, and also create the reg-keys for the
used CLSIDs manualy (by the setup program). I don't need the appID, as
i use CreateObject in VB and pass the servername myself. Now it seems
to work ok.
Nevertheless i think this is the badest solution, as i also have to
adjust the setup procedure every time i add a class or change the
classID.
Also building the proxy/stub and adding the OLESelfRegister to the
version-file did not work, Againe "Class/Interface not registered".
Could it realy be that COM/DCOM dose not implement any solution for
this realy simple problem?