DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 3 of 3

Thread: VBA client for dcom?

  1. #1
    Vincent Tripodi Guest

    VBA client for dcom?

    I want to create a component that resides on an NT4 server and access it
    from a VBA client ... meaning I don't want to specifically create and
    compile a client app which uses the component. I want to instantiate this
    component from a VBA script which is compiled by a proprietary VBA compiler.

    Basically, is it possible for a client app to instantiate a component thru
    DCOM from a VBA script (say Word VBA even) that doesn't get compiled using
    the P&D wizard?

    I was thinking maybe I had to create a dummy setup package for the client to
    get the component registered correctly and then I could access it from VBA?

    Am I making any sense? Thanks.




  2. #2
    Bill Slater Guest

    Re: VBA client for dcom?

    You can take the typelib and VBR files created by VB when you compile the server
    application and register them on the client manually, or as you suggest, by
    creating a 'dummy' install package. Once the TLB is registered, VBA will be able
    to instantiate the objects.

    Vincent Tripodi wrote:

    > I want to create a component that resides on an NT4 server and access it
    > from a VBA client ... meaning I don't want to specifically create and
    > compile a client app which uses the component. I want to instantiate this
    > component from a VBA script which is compiled by a proprietary VBA compiler.
    >
    > Basically, is it possible for a client app to instantiate a component thru
    > DCOM from a VBA script (say Word VBA even) that doesn't get compiled using
    > the P&D wizard?
    >
    > I was thinking maybe I had to create a dummy setup package for the client to
    > get the component registered correctly and then I could access it from VBA?
    >
    > Am I making any sense? Thanks.



  3. #3
    Paul Clement Guest

    Re: VBA client for dcom?

    On Sat, 31 Mar 2001 13:02:17 -0500, "Vincent Tripodi" <vincent.tripodi@extremeconsulting.net> wrote:

    I want to create a component that resides on an NT4 server and access it
    from a VBA client ... meaning I don't want to specifically create and
    compile a client app which uses the component. I want to instantiate this
    component from a VBA script which is compiled by a proprietary VBA compiler.

    Basically, is it possible for a client app to instantiate a component thru
    DCOM from a VBA script (say Word VBA even) that doesn't get compiled using
    the P&D wizard?

    I was thinking maybe I had to create a dummy setup package for the client to
    get the component registered correctly and then I could access it from VBA?

    Am I making any sense? Thanks.



    The answer to your question is yes. You can essentially run this component from any application that
    supports COM and the ability to instantiate the object (such as using CreateObject).

    However, the component will need to be registered (not installed) on the client in order to be
    remoted via DCOM (that is unless you code the server name in your CreateObject statement). The P&D
    Wizard can create this package for you.


    Paul ~~~ pclement@ameritech.net
    Microsoft MVP (Visual Basic)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center