Access 97 on Windows 7 problem
I have installed my program on a Win7 computer. It is supposed to open an Access 97 MDE file and works fine on other machines running the same operating system.
This one comes up with an Error stating: "Microsoft Access has stopped working". The machine has Access 2007 installed.
To overcome this, I changed the shortcut target to call the two files, like this:
“C:\Program Files (x86)\Access 97 Runtime\MSAccess.exe” “C:\ProgramData\invoiceit!
When I run this, the system returns an error stating " can't find the database file "C:\ProgramData\invoiceit!
When I tried to change file association of MDE and MDB files to the runtime Access version, the Win7 system will not accept it.
Would the experts have any information about this issue that might help resolve it?
Help would be greatly appreciated.
This one comes up with an Error stating: "Microsoft Access has stopped working". The machine has Access 2007 installed.
To overcome this, I changed the shortcut target to call the two files, like this:
“C:\Program Files (x86)\Access 97 Runtime\MSAccess.exe” “C:\ProgramData\invoiceit!
When I run this, the system returns an error stating " can't find the database file "C:\ProgramData\invoiceit!
When I tried to change file association of MDE and MDB files to the runtime Access version, the Win7 system will not accept it.
Would the experts have any information about this issue that might help resolve it?
Help would be greatly appreciated.
Peter Chan
Can you install Access 97 on a "Clean" Win 7 OS, that is not having any previous setup of Access 2007?
Did you try it without quotes around the .mde path?
<<This one comes up with an Error stating: "Microsoft Access has stopped working". The machine has Access 2007 installed.>>
When you install multiple versions of Access on the same computer, you generally can get away with it if:
1. Each is stored in a separate directory.
2. The earliest version is installed first.
You can also use Sage Key installer to isolate the versions.
But in your case, I would:
1. Re-install A97 to a directory other than the default (i.e. C:\Program Files (x86)\Office97
2. Then reinstall A2007 using the normal defaults.
Jim.
When you install multiple versions of Access on the same computer, you generally can get away with it if:
1. Each is stored in a separate directory.
2. The earliest version is installed first.
You can also use Sage Key installer to isolate the versions.
But in your case, I would:
1. Re-install A97 to a directory other than the default (i.e. C:\Program Files (x86)\Office97
2. Then reinstall A2007 using the normal defaults.
Jim.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
One other thing you can do by the way is run Access 97 in a Virtual Machine under Windows 7 (free download from Microsoft).
It was meant exactly for things like this.
Jim.
It was meant exactly for things like this.
Jim.
ASKER
Thank you so much for all the comments and suggestions. After some further investigation it turned out that Windows Data Execution Prevention (DEP) was the cause of the errors. The system did not "trust" Access 97 runtime and so tried to switch to the later installed version. That, of course, did not work and the errors piled up.
I am especially thankful for PatHartman's comments regarding the aging. You are quite right, the program is getting too old and I am taking steps, at last, to hurl it into the next century. Although it wasn't the eventual solution, I am accepting your comments as such since the whole mess would not have happened under a much later Access version.
SageKey sell runtime versions as part of their installers, which they call Access Deployment Wizard, for anyone interested. They are at www.sagekey.com
I am especially thankful for PatHartman's comments regarding the aging. You are quite right, the program is getting too old and I am taking steps, at last, to hurl it into the next century. Although it wasn't the eventual solution, I am accepting your comments as such since the whole mess would not have happened under a much later Access version.
SageKey sell runtime versions as part of their installers, which they call Access Deployment Wizard, for anyone interested. They are at www.sagekey.com
ASKER
it wasn't the eventual solution, but it pointed to the real reason for the problem. Thanks for your contribution.