Results 1 to 6 of 6

Thread: Moving from COM to DCOM

  1. #1

    Thread Starter
    Addicted Member
    Join Date
    Oct 2001
    Location
    United Kingdom
    Posts
    141

    Moving from COM to DCOM

    I am quite pleased with myself. I have an ActiveX EXE which runs SQL queries asynchronously and notifies my clients when the query has finished. Not bad eh ?..well for me anyway

    I am now thinking about moving this EXE to a dedicated high powered Server.

    How do I configure the clients to reference the EXE on another machine.

    Is there coding required in the EXE or is it all done for me my DCOM config. program within Windows
    LongyP

  2. #2
    Hyperactive Member FATBOYPEE's Avatar
    Join Date
    May 2001
    Location
    Charleville (Ireland) Still. ANYONE GOT A JOB I CAN HAVE ? GIZA JOB. I CAN DO THAT....
    Posts
    463
    If the High-Power Server capable of supporting VB DLL's ? I.e it's not a Linux/Unix/somsuch machine then to move to DCOM is simple.

    All you need to do in install/deploy your DLL to the new server (not forgetting to configure your database connection of your server etc !!). Open the Client VBP and make a Networked Path reference to the DLL on the new server & re-deploy the client.

    Of course, things to consider when deploying the DLL are any dependencies the DLL may require, connections to Databases etc etc, the load the DLL will have to take... It really depends upon how tight you coded your DLL and what it's for. But assuming your Error Handling etc follows COM rules etc then there should in theory be No problem.

    FATBOYPEE
    Last edited by FATBOYPEE; Nov 8th, 2001 at 04:53 AM.

    Best Bar.....

  3. #3

    Thread Starter
    Addicted Member
    Join Date
    Oct 2001
    Location
    United Kingdom
    Posts
    141
    Thanks for the reply. It had been v. quiet up until then,,I thought I had asked a question dealing with Black Magic.

    I will give this a try. This really sounds too simple. I hope it works.

    Thanks, I will let you know.
    LongyP

  4. #4
    New Member
    Join Date
    Oct 2001
    Location
    Indore
    Posts
    9

    Red face dcom

    Dear

    if u want to go on the dcom then this is very simple
    u hv to register ur exe on the server with dcomcnfg
    utility
    ur client hv install the dcom support and then through
    the clicnfg register the .vbr and .tlb file on client
    now if u make changes in the exe then client will find that reflect
    without any changes
    i think that u ust wanna this
    bye
    sachin

  5. #5
    bipinav
    Guest

    Red face

    hi
    i wonder if a Networked Path reference to the DLL on the new server is made , on which memory space does the DLL open ? If it opens up in the client space , can we tell it's a server dll ??
    Can u please clarify ?
    Thanks
    bips

  6. #6
    New Member
    Join Date
    Oct 2001
    Location
    Indore
    Posts
    9

    Dll will support on MTS

    Dear

    if u want to deploy the DLL then u can od this with the MTS
    and if u hv use EXE then u can do this by DCOM support
    obviosly for dll also and the instance will depend on the instancing property of the class what u hv set
    multiuse,singleuse etc

    Sachin

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width