Re: VB newbie - exposing VB subs to VBA?

From: Maury Markowitz (MauryMarkowitz_at_discussions.microsoft.com)
Date: 02/14/05 

Date: Mon, 14 Feb 2005 06:57:07 -0800

"Ralph" wrote:
> There is no way to avoid 'DCOM', per se, as you will have to create an
> ActiveX component and use COM to connect to it. Using either an ActiveX DLL
> or EXE. Excel is an example of an ActiveX Exe. You would 'connect' to your
> component the same way.

That's fine: the problems that I'm seeing are likely due to the applications
themselves, as opposed to DCOM. This is why I'm interested in the VB path,
because that way I feel I can have more control over the process.

> To create one in VB is very simple, just chose the correct Project Wizard
> when you create the project. Then make sure the component is properly
> registered on each box and configured thru the Computer Managment Console
> (MMC, Component Services Admin, ..., or whatever for your platform).

Is there any way to automate this process? For instance, can VB code call
whatever is needed to complete the registration?

> Not sure what you mean by "fire up a command line app from a remote
> machine". There are various ways to run a remote shell on another computer

This is precisely what I mean. Is there something "built in" that I should
be aware of?

> user. You might want to look at the various COM+ services such as messaging
> for a more easily controlled cross-box communication. But this likely
> over-kill for what you are trying to do.

I also considered SOAP, but setup for many of these sorts of systems tends
to be difficult -- or at least more difficult than DCOM.

Maury

Relevant Pages