Access 97 in Win 7 64 bit

I attempted to install Access 97 ( have to use it due to the applications written in it) in Windows 7 64 bit and apparently because it can't write to the c:\windows\system32 folder the installation fails. I also tried installing it with administrative privileges and it didn't work. I installed it in XP Mode and got the same results.

Initially the installation said that ctl3d32.dll couldn't be installed, then an error saying system.mdw wasn't installed. When I try to create system.mdw using the Workgroup Administrator it fails, probably because it can't write to the /windows/system32 folder.

I am sure this is a common problem but I can't find a solution.

I am a developer so I have a ton of apps to install, but this is the only problem I have with running applications in the 64 bit Windows 7.

Any ideas?

Thanks for your help...

RockyMtnHi said:

...I am sure this is a common problem but I can't find a solution....

Click to expand...

Probably cannot find a solution cause it is not a common problem. Not many people are going to install an application from 1997 on a modern day OS. What you are probably going have to do is create a new virtual machine, not the one that came installed as XP Mode. Might want to use Windows 2000 or even Windows 98...

Dang,
Other than this I have been able to install literally all of my applications in 64 bit Win 7 and have them work like clockwork. I hate to have one app that needs a virtual machine.

If anyone has solved this please pipe in. In the meantime I'm installing Win 98 SE in a virtual machine...

Thanks

I solved it (without the VM)! Access 97 is now running in 64 bit Win 7.

I did this Google search:
install windows inside virtual machine
and clicked on the Windows Virtual PC home page. Then I clicked Help and How To: Windows 7. Next I clicked Make older programs run in Windows 7. I viewed the video on Windows 7 Help & How-to - Microsoft Windows and went the troubleshooting route. Its running fine now.

I ran the troubleshooter on the Workgroup Administrator which allowed me to create the system.mdw that wasn't created on initial install.

What fixed it was allowing permission changes to the /Windows/System32 folder.

So far Windows 7 is a dream. The 8Gb of RAM and quad CPU certainly helps.

I have the same issue! How did you change the permissions on the system32 folder?

I have the same issue here. I tried copying files and changing owners & permissions. Still no luck.

Anyone who has solved this issue please provide detailed steps. Thanks.

Me too

Methinks RockyMtnHI is a bit too high I am having the same issue and wonder if he/she really did what was claimed.

My problem regarding this issue:

a) Trying install without troubleshooting: Windows 7 says not compatible application, and don't let me install

b) With compatibility troubleshooting: Start program button doesn't do anything

My windows version is Windows 7 professional 64 bits. SO, I cannot install office 97 (SR1) in my windows 7 64 bits

That program is 13 years out of date and is not compatible with a 64bit OS... You need to get a later version ... Office 2010 ...

I am all for getting a new version of office, but with access its not that simple. You have to convert the db to go from version to version. With one that out of date, you'd be better off starting from scratch and just importing the data.

Here is what I have done to get Office97 (primarily Access97) to work on Windows7HomePremium and Server2008R2.

Take ownership of C:\windows\System32 and C:\Windows\SysWOW64
Properties - Security - Advanced - Owner - Edit - AdministratorsGroup - Apply - OK - Change permissions - Administrators - Edit - Administrators - ALL - OK - OK

Install Office97 as Custom to C:\Program Files\Microsoft Office NOT C:\Program Files (x86)\Microsoft Office without Outlook (I haven't come up with a solution yet). You will get the CTL3D32.dll error message and maybe some mail error just keep clicking ok. It should say that it was installed successfully.

Copy CTL3D32.DLL and WRKGADM.EXE from C:\Windows\SysWOW64 to C:\Windows\System32
There is no need to overwrite CTL3D32.DLL if it exists.

Before applying Service Pack 2 - sr2bof97.exe, you will need to copy Tahoma fonts from a known good install to C:\Windows\Fonts overwriting if necessary. Apply Service Pack 2.

If you will be using an ACC97 mde, you will need to create an exact folder structure to match the location of any references as they are on the computer that created the mde.

If you need create ODBC connection, be mindful the default ODBC is 64bit and is not 100% compatible with 32bit databases, SQL2005 on Server 2003. I ran into code problems with ADO and the 64bit ODBC. The 32 bit ODBC is located at C:\Windows\SysWOW64\odbcad32.exe

Turn off Data Execution Prevention for msaccess.exe
Start - Control Panel - Advanced system settings - Advanced - Performance - Settings - Data Execution - Navigate to C:\Program Files\Microsoft Office\Office\msaccess.exe

Change the Compatibility for msaccess.exe at C:\Program Files\Microsoft Office\Office to Windows XP (Service Pack 3). Also change the Privilege Level to Run this program as an administrator.

Thanks, MBERG, but the problem is I cannot even install my Office97 software. I only obtain the message 'This file version is not compatible with Windows running version....contact provider'


(sorry, i'm translating the message from the windows 7 spanish version)

Access 97 in Windows 7

Hi Mberg,

I tried your method, but after I chose the c:\Program Files\Microsoft Office, I got the message:

"This operating system does not meet the minimum requirements to run Office 97. Please check the minimum requirements section of the README.TXT or README.HLP on this CD for further details."

I am trying to install Access 97 SR2 which I have a standalone CD (separate from the rest of MS Office).

I did get Access 97 to install in compatibility mode, but I'd love to be able to use it without compatibility mode, if that's possible.

Any further ideas? Thanks!

MBERG said:

Here is what I have done to get Office97 (primarily Access97) to work on Windows7HomePremium and Server2008R2.

Take ownership of C:\windows\System32 and C:\Windows\SysWOW64
Properties - Security - Advanced - Owner - Edit - AdministratorsGroup - Apply - OK - Change permissions - Administrators - Edit - Administrators - ALL - OK - OK

Install Office97 as Custom to C:\Program Files\Microsoft Office NOT C:\Program Files (x86)\Microsoft Office without Outlook (I haven't come up with a solution yet). You will get the CTL3D32.dll error message and maybe some mail error just keep clicking ok. It should say that it was installed successfully.

Copy CTL3D32.DLL and WRKGADM.EXE from C:\Windows\SysWOW64 to C:\Windows\System32
There is no need to overwrite CTL3D32.DLL if it exists.

Before applying Service Pack 2 - sr2bof97.exe, you will need to copy Tahoma fonts from a known good install to C:\Windows\Fonts overwriting if necessary. Apply Service Pack 2.

If you will be using an ACC97 mde, you will need to create an exact folder structure to match the location of any references as they are on the computer that created the mde.

If you need create ODBC connection, be mindful the default ODBC is 64bit and is not 100% compatible with 32bit databases, SQL2005 on Server 2003. I ran into code problems with ADO and the 64bit ODBC. The 32 bit ODBC is located at C:\Windows\SysWOW64\odbcad32.exe

Turn off Data Execution Prevention for msaccess.exe
Start - Control Panel - Advanced system settings - Advanced - Performance - Settings - Data Execution - Navigate to C:\Program Files\Microsoft Office\Office\msaccess.exe

Change the Compatibility for msaccess.exe at C:\Program Files\Microsoft Office\Office to Windows XP (Service Pack 3). Also change the Privilege Level to Run this program as an administrator.

Click to expand...

RockyMtnHi said:

I attempted to install Access 97 ( have to use it due to the applications written in it) in Windows 7 64 bit and apparently because it can't write to the c:\windows\system32 folder the installation fails. I also tried installing it with administrative privileges and it didn't work. I installed it in XP Mode and got the same results.

Initially the installation said that ctl3d32.dll couldn't be installed, then an error saying system.mdw wasn't installed. When I try to create system.mdw using the Workgroup Administrator it fails, probably because it can't write to the /windows/system32 folder.

I am sure this is a common problem but I can't find a solution.

I am a developer so I have a ton of apps to install, but this is the only problem I have with running applications in the 64 bit Windows 7.

Any ideas?

Thanks for your help...

Click to expand...

I have an "OEM" version of Office 97 Professional and have successfully installed and run all its features including Access (that is except Outlook, which I don't use).

Moreover, I have installed it not only on Windows 7 32 and 64-bit, but also have run it on Vista and as well most recently on Windows 8 64-bit.

I do use a registry hack that gives me a right-click selection to "Take ownership of this folder" and used it on the Windows "Fonts" folder and the "System32" folder. I also did the same on the Office folder in Program Files (or Program Files (x86) as appropriate).

As well, I use the Properties -> Compatibility Tab to run all installs and patches using the Windows 95 mode and Administrator.

The only "problems" I have had are: 1) installing the SR-2 patch, and 2) in Windows 8 the "SendKeys" macro function does not work.

I have solved the problem with the SR2 patch by modifying the "FileList.txt" file before running the patch. (I will share the steps to do this if anyone wants them.)

Can you give step-by-step instructions?

When I try to install Access 97 with SR-2 patch, I get a message "This operating system does not meet the minimum requirements to run Office 97. Please check the minimum requirements section fot he README.TXT or README.HLP on this CD for further details". I am using an up-to-date computer. Step by step instructions would be very helpful. Thanks!

Please tell me you are trying to move your access97 stuff to something from the past decade????

Just so you are aware Windows 8 will be microsofts last 32bit OS. If you really need it, thats what app-v and thinapp are for. just put the mdb file on a file share and allow the virtualized app access to the share.

pbr2000 said:

When I try to install Access 97 with SR-2 patch, I get a message "This operating system does not meet the minimum requirements to run Office 97. Please check the minimum requirements section fot he README.TXT or README.HLP on this CD for further details". I am using an up-to-date computer. Step by step instructions would be very helpful. Thanks!

Click to expand...

It sounds like my installation may differ from yours in that I am installing Access 97 from my disk of Office 97 Professional "OEM". It does NOT contain any service releases of any kind. (I've always had to apply these after initial install.)

My installs on XP, Vista and Windows 7 have been 32-bit. The 64-bit install I've done was on Windows 8 Consumer Preview and it went flawlessly. I was even able to apply SR1 and SR3 after install. (I had to modify permissions and "filelist.txt" to get SR3 to install.)

After you posted, I decided to install on 64-bit Windows 7 and see if it would go the same as on Windows 8.

It did not. I received the "CTL3D32.DLL" error discussed elsewhere and "fixed" it per the other posts. (Although I also tested my install before I did the fix and everything seemed to work OK.)

I was not able to install SR3 even using the method that worked on Windows 8, so I'm afraid I don't have help to give you.

Word, Access, Excel and Power Point (97) are all working OK without the service pack(s). I don't use Outlook, but for kicks I tried to include it in the install but I could not even get it to start up.

So the bottom line is that, for me anyway, Access 97 will work on 64-bit WIndows 7 by using my Office 97 Professional OEM install that contains no service releases.

I hope that this info helps some.

ccatlett1984 said:

Please tell me you are trying to move your access97 stuff to something from the past decade????

Just so you are aware Windows 8 will be microsofts last 32bit OS. If you really need it, thats what app-v and thinapp are for. just put the mdb file on a file share and allow the virtualized app access to the share.

Click to expand...

I have a pretty involved Access database (for personal use) that was created on Access 2.0 and, with a few tweaks, now also runs perfectly on Access 97. I programmed it with many macro functions (a mistake I see now), and since it's been over 15 years since doing it, I'm not sure I'll ever get it to work like it does on the "newer" versions of Access.

Then also, there are the pervasive "Authentication" issues that go along with the newer versions of Office and these do not have to be dealt with when I use Office 97 (like for my experimental WIndows 8 install).

"I am all for getting a new version of office, but with access its not that simple. You have to convert the db to go from version to version. With one that out of date, you'd be better off starting from scratch and just importing the data."

Converting Access files from 97 or indeed 2003 to a more modern format is a terminal pain in the posterior.
However, despite all the pleas that it's an impossible process to automate ... It can be automated.

The problem is that Access does not have full VBA ActiveX automation and object model.
Therefore it seems impossible to script a bulk database conversion routine.

I read many articles on this problem which all said "convert every database manually".
Well, I tried ... but I have one main database with 8000 sub databases used as an OLE file store.
Manually typing every name 8000 times was not an option.
You have to actually type the new file name.

Since the files contain zipped OLE objects "Exporting all the data and rebuilding"
is not an option either - well, it's probably possible but would be hugely CPU and time consuming.

After RSI set in on having to type every export name ...
I tried making a mirror directory of empty files so that I wouldn't have to actually type every file name.
This kind of worked if I clicked on the file name and then right clicked delete within the file select window.
The save routine wont let you overwrite an existing file - helpful!
This was tedious but doable ... I found I could get through about 100 files a day.
Even at that rate you're looking at 3 months in man hours to convert 8000 access 97 files to 2003.
Why did they change the file extension for XLS and MDB for newer versions ... dumb ...but let's not go there...

There is a solution. Access has a command line script option.
The batch file needs to read something like this

C:
CD C:\
CD Program Files (x86)
CD Microsoft Office
CD OFFICE11
msaccess.exe L:\LogWorldOLE\WELL1.MDB /convert C:\LogWorldOLE\WELL1.MDB

Bingo.

Of course you still have to press OK 8000 times.
And the purists will whinge that the only way to convert a database properly is to go through the front end.
But frankly that's not viable will 8000 files so I converted the main database file manually
and the others by commandline.
All of them are very simple files though with no forms or relationships.
So it might fall over with something more complicated
Worked for me anyway

At the end of the line I have the old files as well so if any haven't converted properly I can go back and do individual ones manually .... which has got to be quicker than typing all the names again manually and going through the front end which must take about a man year for 8000 files.

MBERG said:

Here is what I have done to get Office97 (primarily Access97) to work on Windows7HomePremium and Server2008R2.

Take ownership of C:\windows\System32 and C:\Windows\SysWOW64
Properties - Security - Advanced - Owner - Edit - AdministratorsGroup - Apply - OK - Change permissions - Administrators - Edit - Administrators - ALL - OK - OK

Install Office97 as Custom to C:\Program Files\Microsoft Office NOT C:\Program Files (x86)\Microsoft Office without Outlook (I haven't come up with a solution yet). You will get the CTL3D32.dll error message and maybe some mail error just keep clicking ok. It should say that it was installed successfully.

Copy CTL3D32.DLL and WRKGADM.EXE from C:\Windows\SysWOW64 to C:\Windows\System32
There is no need to overwrite CTL3D32.DLL if it exists.

Before applying Service Pack 2 - sr2bof97.exe, you will need to copy Tahoma fonts from a known good install to C:\Windows\Fonts overwriting if necessary. Apply Service Pack 2.

If you will be using an ACC97 mde, you will need to create an exact folder structure to match the location of any references as they are on the computer that created the mde.

If you need create ODBC connection, be mindful the default ODBC is 64bit and is not 100% compatible with 32bit databases, SQL2005 on Server 2003. I ran into code problems with ADO and the 64bit ODBC. The 32 bit ODBC is located at C:\Windows\SysWOW64\odbcad32.exe

Turn off Data Execution Prevention for msaccess.exe
Start - Control Panel - Advanced system settings - Advanced - Performance - Settings - Data Execution - Navigate to C:\Program Files\Microsoft Office\Office\msaccess.exe

Change the Compatibility for msaccess.exe at C:\Program Files\Microsoft Office\Office to Windows XP (Service Pack 3). Also change the Privilege Level to Run this program as an administrator.

Click to expand...

Copy CTL3D32.DLL and WRKGADM.EXE from C:\Windows\SysWOW64 to C:\Windows\System32
There is no need to overwrite CTL3D32.DLL if it exists.

That's not right!! If office 97 (32bits application) tries to access C:\Windows\System32 it actually accesses C:\Windows\SysWOW64!

C:\Windows\System32 : contains 64bits stuff
C:\Windows\SysWOW64: all 32bits stuff

Install in compatibility mode!