Help with Dcom set up


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 4 of 4

Thread: Help with Dcom set up

  1. #1
    Debbie Guest

    Help with Dcom set up


    We have created a small exe application in vb6 that uses some dlls residing
    on the same machine to
    connect to an informix database on a unix machine. We had to use the ole
    db driver for odbc drivers.
    The application runs perfectly on the win98 machine it was designed on. However,
    when we try to run
    the application on another machine we get error 13 type mismatch. We have
    installed the informix
    drivers on the machine and set up a system dsn on the machine. We were able
    to get the application
    to run on one win 95 machine but not on any other machine. When we did the
    package & deployment
    wizard we were told to make sure dcom 98 was set up on the machine. On a
    win95 machine we installed
    dcom95 version 1.3. But the program still fails. Any help would be appreciated!
    Still new at this.



    Share on Google+

  2. #2
    ranga raghunathan Guest

    Re: Help with Dcom set up


    "Debbie" <dbentz@sjcworknet.org> wrote:
    >
    >We have created a small exe application in vb6 that uses some dlls residing
    >on the same machine to
    >connect to an informix database on a unix machine. We had to use the ole
    >db driver for odbc drivers.
    >The application runs perfectly on the win98 machine it was designed on.

    However,
    >when we try to run
    >the application on another machine we get error 13 type mismatch. We have
    >installed the informix
    >drivers on the machine and set up a system dsn on the machine. We were

    able
    >to get the application
    >to run on one win 95 machine but not on any other machine. When we did the
    >package & deployment
    >wizard we were told to make sure dcom 98 was set up on the machine. On a
    >win95 machine we installed
    >dcom95 version 1.3. But the program still fails. Any help would be appreciated!
    >Still new at this.
    >
    >
    >

    couple of suggestions
    a )check if the dll is registered in the machine - i am not sure if the pdw
    will register the dlls ..
    b) if you have vb installed in the problem machine, step thru the code and
    see which line causes this problem ..
    c)independent of the above 2 suggestions, the fact that you get a type mismatch
    error does not mean that the problem is with dcom - it may be that you are
    supplying the wrong datatype to a procedure ..
    hope this helps
    ranga

    Share on Google+

  3. #3
    jeff Guest

    Re: Help with Dcom set up


    "ranga raghunathan" <ranga1@msn.com> wrote:
    >
    >"Debbie" <dbentz@sjcworknet.org> wrote:
    >>
    >>We have created a small exe application in vb6 that uses some dlls residing
    >>on the same machine to
    >>connect to an informix database on a unix machine. We had to use the ole
    >>db driver for odbc drivers.
    >>The application runs perfectly on the win98 machine it was designed on.

    >However,
    >>when we try to run
    >>the application on another machine we get error 13 type mismatch. We have
    >>installed the informix
    >>drivers on the machine and set up a system dsn on the machine. We were

    >able
    >>to get the application
    >>to run on one win 95 machine but not on any other machine. When we did

    the
    >>package & deployment
    >>wizard we were told to make sure dcom 98 was set up on the machine. On

    a
    >>win95 machine we installed
    >>dcom95 version 1.3. But the program still fails. Any help would be appreciated!
    >>Still new at this.
    >>
    >>
    >>

    >couple of suggestions
    >a )check if the dll is registered in the machine - i am not sure if the

    pdw
    >will register the dlls ..
    >b) if you have vb installed in the problem machine, step thru the code and
    >see which line causes this problem ..
    >c)independent of the above 2 suggestions, the fact that you get a type mismatch
    >error does not mean that the problem is with dcom - it may be that you are
    >supplying the wrong datatype to a procedure ..
    >hope this helps
    >ranga
    >


    Make sure you have the save version of MDAC on both machines. I have noticed
    recently that components compiled under MDAC2.5 will not run successfully
    on machines that are using MDAC2.1 - type mismatch errors abound. This occurs
    when you reference the 2.1 typelib on the MDAC 2.5 machine, compile the DLL
    and then try to execute on the 2.1 machine...
    Share on Google+

  4. #4
    Mario Lucio Guest

    Re: Help with Dcom set up


    "jeff" <jeff.lammers@penske.com> wrote:
    >
    >"ranga raghunathan" <ranga1@msn.com> wrote:
    >>
    >>"Debbie" <dbentz@sjcworknet.org> wrote:
    >>>
    >>>We have created a small exe application in vb6 that uses some dlls residing
    >>>on the same machine to
    >>>connect to an informix database on a unix machine. We had to use the

    ole
    >>>db driver for odbc drivers.
    >>>The application runs perfectly on the win98 machine it was designed on.

    >>However,
    >>>when we try to run
    >>>the application on another machine we get error 13 type mismatch. We

    have
    >>>installed the informix
    >>>drivers on the machine and set up a system dsn on the machine. We were

    >>able
    >>>to get the application
    >>>to run on one win 95 machine but not on any other machine. When we did

    >the
    >>>package & deployment
    >>>wizard we were told to make sure dcom 98 was set up on the machine. On

    >a
    >>>win95 machine we installed
    >>>dcom95 version 1.3. But the program still fails. Any help would be appreciated!
    >>>Still new at this.
    >>>
    >>>
    >>>

    >>couple of suggestions
    >>a )check if the dll is registered in the machine - i am not sure if the

    >pdw
    >>will register the dlls ..
    >>b) if you have vb installed in the problem machine, step thru the code

    and
    >>see which line causes this problem ..
    >>c)independent of the above 2 suggestions, the fact that you get a type

    mismatch
    >>error does not mean that the problem is with dcom - it may be that you

    are
    >>supplying the wrong datatype to a procedure ..
    >>hope this helps
    >>ranga
    >>

    >
    >Make sure you have the save version of MDAC on both machines. I have noticed
    >recently that components compiled under MDAC2.5 will not run successfully
    >on machines that are using MDAC2.1 - type mismatch errors abound. This

    occurs
    >when you reference the 2.1 typelib on the MDAC 2.5 machine, compile the

    DLL
    >and then try to execute on the 2.1 machine...



    Hi,

    I get that problem too, but it's was not dcom configuration.
    In my case, the problem was the international settings in the date and time
    formats in windows environment.
    When i make all the same, that problem was solved.

    Good luck !


    Share on Google+

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