Judgester
asked on
Install Access 1.1 on Win XP?
I have some very old programs to manage for a client one of which uses MS Access 1.1 in a VB3 app. I have had to keep a Win95 machine around just for this one program :( Having just purchased a new machine (XP Pro) I would love to get Access 1.1 installed on it so I can finally have only a single machine under my desk.
Access 1.0 installed no problem. But when I try to run the upgrade to Access 1.1 I get a message saying I have to install a Windows for Workgroups driver from DOS! I've tried installing the driver from a DOS window. The driver install completed without an error message but the Access 1.1 upgrade install still gives the same error message.
I know I should convince the customer to update their software but if they didn't do it 10 years ago they sure will not do it now!
Any help would be appreciated.
Access 1.0 installed no problem. But when I try to run the upgrade to Access 1.1 I get a message saying I have to install a Windows for Workgroups driver from DOS! I've tried installing the driver from a DOS window. The driver install completed without an error message but the Access 1.1 upgrade install still gives the same error message.
I know I should convince the customer to update their software but if they didn't do it 10 years ago they sure will not do it now!
Any help would be appreciated.
ASKER
Thanks Jim, I agree but this is not an option unfortunately.
Jim
Jim
Judgester,
Some clients can be stubborn...
What if you copy the install files to a folder on your hard drive and then right-click and set the compatibility to Windows 95 before launching the install?
Run Older Programs on Windows XP
http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/appcompat.mspx
Hope that helps.
Scot
Some clients can be stubborn...
What if you copy the install files to a folder on your hard drive and then right-click and set the compatibility to Windows 95 before launching the install?
Run Older Programs on Windows XP
http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/appcompat.mspx
Hope that helps.
Scot
Judgester,
Does the app run OK in 1.0?
If yes, then why not leave it in 1.0?
What I mean is:
If there are no real Visual or Functional differences between 1.0 and 1.1 (as the increment would imply), then just leave it in 1.0.
Jeffrey Coachman
Does the app run OK in 1.0?
If yes, then why not leave it in 1.0?
What I mean is:
If there are no real Visual or Functional differences between 1.0 and 1.1 (as the increment would imply), then just leave it in 1.0.
Jeffrey Coachman
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Scot - I read the article but do not think this is applicable because the problem is with the Access 1.1 install (upgrade from Access 1.0)
Jeffery - Hmmm... I guess I had not thought of this. I will give it a try. The app (VB3) is one that I do have to make occasional changes to, recompile and create an install for the updated file. However if I can make changes to the current MDB files created with Access 1.1 using Access 1.0 and then they work with the app then I am home free and do not have to worry about installing Access 1.1 !
Thanks for the clear thinking on this. (I feel a little stupid.)
gustav - You are exactly correct. WFWDRV.DRV is the problem. THe file has to be replaced in DOS because it gets loaded (apparently) by Windows. Now if I could just figure out how to get to a DOS prompt that will recognize my C: drive I could try this solution.
Jeffery - Hmmm... I guess I had not thought of this. I will give it a try. The app (VB3) is one that I do have to make occasional changes to, recompile and create an install for the updated file. However if I can make changes to the current MDB files created with Access 1.1 using Access 1.0 and then they work with the app then I am home free and do not have to worry about installing Access 1.1 !
Thanks for the clear thinking on this. (I feel a little stupid.)
gustav - You are exactly correct. WFWDRV.DRV is the problem. THe file has to be replaced in DOS because it gets loaded (apparently) by Windows. Now if I could just figure out how to get to a DOS prompt that will recognize my C: drive I could try this solution.
Oh, I believe to remember that 1.1 was if not a major then an important (bugfix) upgrade to 1.0.
If you cannot see drive C: in a DOS box you may need to log on as the Administrator.
You may also need to boot in safe mode if access to the file is denied even for the Administrator.
/gustav
If you cannot see drive C: in a DOS box you may need to log on as the Administrator.
You may also need to boot in safe mode if access to the file is denied even for the Administrator.
/gustav
ASKER
Got it installed!
Sorry for my ignorance on XP boot options. Here is what I did...
1. Restart computer hitting F8 several times to access the boot options menu.
2. Chose to boot in Safe Mode with Commmand prompt.
3. Put the OCDB diskette that came with Access 1.1 in.
4. Logged on to the diskette drive a:
5. Ran the the Windows for Workgroups driver install... WFWDRV C:\Windows
6. Received message that the correct driver had been installed.
7. Normal reboot in XP.
8. Access 1.1 upgrade installed without problems!
Thanks for all your help!
Sorry for my ignorance on XP boot options. Here is what I did...
1. Restart computer hitting F8 several times to access the boot options menu.
2. Chose to boot in Safe Mode with Commmand prompt.
3. Put the OCDB diskette that came with Access 1.1 in.
4. Logged on to the diskette drive a:
5. Ran the the Windows for Workgroups driver install... WFWDRV C:\Windows
6. Received message that the correct driver had been installed.
7. Normal reboot in XP.
8. Access 1.1 upgrade installed without problems!
Thanks for all your help!
That sounds right. Thanks for the feedback.
/gustav
/gustav
Windows '95 and above, including XP, is a 32-bit operating system.
A better approach would be to upgrade your Access app to at minimum Access 2000.
Hope this helps.
-Jim