Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!
  1. Monthly (Recurring) Target: $300 :: Achieved: $95
      Become a Supporter    ::   Make a Contribution   

Problems with a JET-ODBC-Connection and Access97-Runtime

Discussion in 'Information Technology' started by Andreas Lauffer, Nov 17, 2005.

  1. Andreas Lauffer

    Andreas Lauffer
    Expand Collapse
    Guest

    I have a very strange problem with a JET-ODBC-Connection.
    Using Access97-Runtime, we connect the table with a
    DSN-less-ODBC-Connection to SQLServer 2000 SP3.
    The Application runs on a Windows Server 2003 Terminal-Server with
    CITRIX Metaframe.
    Office 2003 is also installed (no Access2003)
    And now the problem:
    -------------------------------------------------------
    When our application is installed anew, the ODBC-Connection works fine.
    When I start any Office2003-Application like Winword, the system files
    MSJINT35.DLL and MSJTER35.DLL are changed. (I used ashampoo Uninstaller
    Suite to check this issue).
    Afterwards, our Application doesn't run anymore, the Application quits
    without any error.
    If I copy the MSJINT35.DLL anew from the install-directory, our
    application runs again correctly.
    The strange thing is, that the "changed" MSJINT35.DLL is exactly the
    same as the original file. Version, Metadata, Language, Filesize, and
    even a Hex-based-compare result that the files are identically.
    Nevertheless, a copy of the file into system32 is a workaround to fix
    the problem for a few hours.
    ---------------------------------------------------------
    Does anyone has any idea? PLEASE HELP!
     
  2. Loading...

    Similar Threads Forum Date
    Sikh News Sikhs Face Problems While Carrying Kirpans In Khyber-Pakhtunkhwa - SikhSiyasat.Net Breaking News Jul 29, 2016
    "Dasam" Granth - A Look At The Core Problems Dasam Granth Oct 21, 2015
    Problems In Life Sikh Sikhi Sikhism Apr 13, 2015
    Muslim Girl-Sikh Boy Marriage Problems- Please Help! Love & Marriage Oct 12, 2012
    Problems with Sikh Historiography-prof Jagdish Singh Sikh Video Aug 31, 2012

  3. Ron Hinds

    Ron Hinds
    Expand Collapse
    Guest

    How are you installing the app? I use Wise Install Builder, which installs
    the Access 97 runtime into it's own folder - C:\Program Files\Access 97
    Runtime. It installs the DLLs in question into that folder, too. The reason
    being - when an app looks for DLL's it starts with the folder the app
    started in, then looks in the folders in the PATH environment variable (e.g.
    System32). You could probably solve your problem by having your installer
    put the DLLs in question into the Runtime folder.

    "Andreas Lauffer" <alweb01@online.de> wrote in message
    news:1132133394.166634.268470@z14g2000cwz.googlegroups.com...
    > I have a very strange problem with a JET-ODBC-Connection.
    > Using Access97-Runtime, we connect the table with a
    > DSN-less-ODBC-Connection to SQLServer 2000 SP3.
    > The Application runs on a Windows Server 2003 Terminal-Server with
    > CITRIX Metaframe.
    > Office 2003 is also installed (no Access2003)
    > And now the problem:
    > -------------------------------------------------------
    > When our application is installed anew, the ODBC-Connection works fine.
    > When I start any Office2003-Application like Winword, the system files
    > MSJINT35.DLL and MSJTER35.DLL are changed. (I used ashampoo Uninstaller
    > Suite to check this issue).
    > Afterwards, our Application doesn't run anymore, the Application quits
    > without any error.
    > If I copy the MSJINT35.DLL anew from the install-directory, our
    > application runs again correctly.
    > The strange thing is, that the "changed" MSJINT35.DLL is exactly the
    > same as the original file. Version, Metadata, Language, Filesize, and
    > even a Hex-based-compare result that the files are identically.
    > Nevertheless, a copy of the file into system32 is a workaround to fix
    > the problem for a few hours.
    > ---------------------------------------------------------
    > Does anyone has any idea? PLEASE HELP!
    >
     
Since you're here... we have a small favor to ask...

More people are visiting & reading SPN than ever but far fewer are paying to sustain it. Advertising revenues across the online media have fallen fast. So you can see why we need to ask for your help. Donating to SPN's is vote for free speech, for diversity of opinions, for the right of the people to stand up to religious bigotry. Without any affiliation to any organization, this constant struggle takes a lot of hard work to sustain as we entirely depend on the contributions of our esteemed writers/readers. We do it because we believe our perspective matters – because it might well be your perspective, too... Fund our efforts and together we can keep the world informed about the real Sikh Sikhi Sikhism. If everyone who writes or reads our content, who likes it, helps us to pay for it, our future would be much more secure. Every Contribution Matters, Contribute Generously!

    Become a Supporter      ::     Make a Contribution     



Share This Page