Results 1 to 9 of 9

Thread: XP Problem! *resolved*

  1. #1

    Thread Starter
    Frenzied Member sebs's Avatar
    Join Date
    Sep 2000
    Location
    Aylmer,Qc
    Posts
    1,606

    XP Problem! *resolved*

    Hi people !

    My boss just re-install a couple of pc at one of our client and installed Win XP on it!

    So he re-installed the program that we did for them and it use MS Access for DB !

    But when he runs the program, it gives a Run-Time error 76 !

    Is it because i need to re-installed a component ?

    Did it happend to one of you ?

    tx
    Last edited by sebs; Jun 20th, 2003 at 09:56 AM.

  2. #2
    I'm about to be a PowerPoster! kleinma's Avatar
    Join Date
    Nov 2001
    Location
    NJ - USA (Near NYC)
    Posts
    23,373
    how did you package your program??? the PDW??? did he install sp1 and other windows updates to the XP machine?

    your not giving much info

  3. #3
    Lively Member Bootking's Avatar
    Join Date
    Mar 2003
    Location
    Marquette University
    Posts
    90
    In the properties for the EXE, you can set it to run in compatibility for a previous Windows operating system. It works most of the time to fix XP-related run time errors.
    Check out my band's website!
    Walter Walker Band

  4. #4
    I'm about to be a PowerPoster! kleinma's Avatar
    Join Date
    Nov 2001
    Location
    NJ - USA (Near NYC)
    Posts
    23,373
    Originally posted by Bootking
    In the properties for the EXE, you can set it to run in compatibility for a previous Windows operating system. It works most of the time to fix XP-related run time errors.
    no that wont solve a runtime error like that.. .there is probably an issue with MDAC or some portion of the database connectivity

  5. #5

    Thread Starter
    Frenzied Member sebs's Avatar
    Join Date
    Sep 2000
    Location
    Aylmer,Qc
    Posts
    1,606
    tx for all the replies guys !

    kleinma, the installation is made from a installation that i did a long time ago, i use InnoSetup now

    It's a DB problem for sure, so like you said, it's problably just a MDAC problem, when you install XP, does it install MS Access 2000 components ?

  6. #6
    I'm about to be a PowerPoster! kleinma's Avatar
    Join Date
    Nov 2001
    Location
    NJ - USA (Near NYC)
    Posts
    23,373
    Originally posted by sebs
    tx for all the replies guys !

    kleinma, the installation is made from a installation that i did a long time ago, i use InnoSetup now

    It's a DB problem for sure, so like you said, it's problably just a MDAC problem, when you install XP, does it install MS Access 2000 components ?

    nope.. doesn't install any access components.. access is a seperate application than windows...so they dont include it.. it SHOULD however install MDAC for sure... but perhaps the versions are different.. do you know what version of MDAC your app uses?? if you install that one it might clear up the problem

  7. #7

    Thread Starter
    Frenzied Member sebs's Avatar
    Join Date
    Sep 2000
    Location
    Aylmer,Qc
    Posts
    1,606
    Yeah, well my setup detect if you have MDAC installed, and intall it you don't have it, so i guess he installed it !

    here's the version

    2.1.2.4202.3

    should it be a different one since it's on XP, problably

    cuz, lately, another of our client had installed XP, and i had to update the Calendar component !

  8. #8
    Addicted Member
    Join Date
    Apr 1999
    Posts
    178
    From MSDN

    "MDAC 2.7 RTM is pre-installed in Windows XP; because the MDAC files are Windows File Protection files, MDAC 2.7 RTM is the earliest version that you can install on Windows XP."


    "Starting with Microsoft Data Access Components (MDAC) version 2.6, MDAC no longer contains Jet components. In other words, MDAC 2.6 and 2.7 do not include Microsoft Jet, Microsoft Jet OLE DB Provider, and the ODBC Desktop Database Drivers."

    You may need to install jet.

  9. #9

    Thread Starter
    Frenzied Member sebs's Avatar
    Join Date
    Sep 2000
    Location
    Aylmer,Qc
    Posts
    1,606
    Hi guys !

    I'm so sorry, i never looked, but I should of, error 76 is a 'Path Not Found' !

    The problem is, the guy that did the app, was a student(so he was learning) and when reading the .ini file for the database path, he had hardcoded "C:\WINNT\system32" instead of using the API to find the windows folder, so XP it's "C:\Windows\system32", so i just changed the app a little bit to use the API and now everything is fine!

    thank you for all your help

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