instancing DCOM components

[Craig Ling]

I have created and installed several DCOM components in VB on one machine,
called machine A, to be called by another VB app on a different machine (machine
B), but think that something is going wrong with how I am calling them.
I have found that the only way I can get the components to work is to export
the component as an application proxy from DTC (I am running Win 2000 on
both machines) on machine A, and install it on the other machine B. Now,
when I run my VB app, it works fine. I have heard that I shouldn't have
to install this proxy on machine A to get it to work, I should be able to
get component access from machine B to A without this step. Any ideas?
It would be greatly appreciated.

Also, I would like to perform the same thing in ASP, have a component reside
on one machine, and still be able to access it from the web server, but I
am having similar problems there too.
Thank you in advance.
Craig

[Bill Slater]

Client B needs the proxy registered on it in order to be able to instantiate on
object on A. When DCOM needs to make a instantiation call to a remote machine it
requires the CLSID of the object it is calling. The only way the client can get this
is if the object's typelib is registered on the client.

HTH

Craig Ling wrote:

> I have created and installed several DCOM components in VB on one machine,
> called machine A, to be called by another VB app on a different machine (machine
> B), but think that something is going wrong with how I am calling them.
> I have found that the only way I can get the components to work is to export
> the component as an application proxy from DTC (I am running Win 2000 on
> both machines) on machine A, and install it on the other machine B. Now,
> when I run my VB app, it works fine. I have heard that I shouldn't have
> to install this proxy on machine A to get it to work, I should be able to
> get component access from machine B to A without this step. Any ideas?
> It would be greatly appreciated.
>
> Also, I would like to perform the same thing in ASP, have a component reside
> on one machine, and still be able to access it from the web server, but I
> am having similar problems there too.
> Thank you in advance.
> Craig

[Randy Coates]

Try looking at Remote Data Services and the Dataspace object

http://msdn.microsoft.com/library/ps...k/rdso3m79.htm
and
http://msdn.microsoft.com/library/ps...k/rdsm6pre.htm

In VB client code, go to Project >> References...
Select "Microsoft Remote Data Services x.x Library"
Create a dataspace (say it's name is objDS)
Call objDS.CreateObject("your object's prog ID", "server A name")

Randy Coates
Anexinet (www.anexinet.com)