Office 2007 and Access 97

[Mark]

I received a new laptop with Vista Home Premium Edition and Microsoft Office
for Small Businesses 2007. I have a licensed copy of Microsoft Office
Professional 97 which I had installed on my old computer.

My question: is there any way I can I use my licensed copy of Microsoft
Office Professional 97 to install Access97 on my new laptop without creating
problems for the system files for Office for Small Businesses 2007?

If yes, what about SR2 and the jet update that came out for Access97?

Thank you,
Mark

 

[Mark]

I know that on Vista I have to run both setup and msaccess.exe as
Administrator.

I don't have the info at home, but at work I printed a thread that explains
how to temporarily replace certain Vista fonts with earlier versions in
order to either install Access 97, or the SR2 for Access 97 (I forget
which).

I believe I have to also first uninstall Office 2007, install Access 97, and
then reinstall Office 2007 -- is this correct?

I'm not sure about the Access 97 SR2 and the jet update. Do I also install
both of those before reinstalling Office 2007?

Mark

 

[Douglas J. Steele]

There should be no need to uninstall Office 2007 first.

To avoid problems, it was (may still be) necessary to rename the
Haettenschweiler font (aka Hatten). See
http://support.microsoft.com/?id=141373

 

[Mark]

Thank you, Douglas. That's good news.
What about the SR2 and jet update that were issued for Access 97?
Mark

 

[Douglas J. Steele]

What about them? Yes, you need to install them. Since you don't need to
uninstall Office 2007, your question "Do I also install both of those before
reinstalling Office 2007?" is irrelevant.

 

[Mark]

Thank you, Doug.
Mark

What about them? Yes, you need to install them. Since you don't need to
uninstall Office 2007, your question "Do I also install both of those before
reinstalling Office 2007?" is irrelevant.

 

[David W. Fenton]

To avoid problems, it was (may still be) necessary to rename the
Haettenschweiler font (aka Hatten). See
http://support.microsoft.com/?id=141373

You don't have to use that font, just any file that will trigger the
installer to recopy the files. That font is the one that MS chose in
its KB article, I think, and all its changed name does is trigger
the subroutine that recopies files and happens to fix the licensing
issue along the way. There's nothing inherent to that particular
font file that is related to the problem itself.

At least, that's how MichKa explained it (if I'm remembering
correctly).

 

[Douglas J. Steele]

You don't have to use that font, just any file that will trigger the
installer to recopy the files. That font is the one that MS chose in
its KB article, I think, and all its changed name does is trigger
the subroutine that recopies files and happens to fix the licensing
issue along the way. There's nothing inherent to that particular
font file that is related to the problem itself.

At least, that's how MichKa explained it (if I'm remembering
correctly).

Interesting. I don't remember seeing that before.

Thanks, David.