[MikeF1986]

I have a new computer - HP Pavilion Media Center with dual core AMDs, 2 gigs of memory, 300 gig HD, and MS XP Media Center Edition 2005 with “update rollup 2.”


I am reinstalling programs that had been on the old computer to the new one (all fresh installs). I have MS Office 2003 at home, but my workplace is standardized on Office 97. I need to have Access 97 co-existing peacefully on my home computer as well as the Office 2003 suite.

I have been unable to install Access 97 from its original CD. I tried to install Access 97  before  installing the MS Office 2003 suite (or ANY other programs as well). I did a custom install and put it in its own unique directory. Here are the error messages I got.

“WORKGROUP ADMINISTRATOR: An error has occurred at changing workgroup database.”

Followed by:

“WORKGROUP ADMINISTRATOR:  Setup couldn’t create a SYSTEM.MDW file. After Setup is completed, reboot your computer, then run the Workgroup Administrator before you run this application. (-1011)”

The workgroup administrator begat:

   “Htmlmarq.ocx was unable to register itself in the system registry.”

In desperation I then tried the SR1 update for Office 97 and got:

“Microsoft Access can’t find the visual Basic for Applications dynamic-link library (DLL)  Vba332.  Rerun the Microsoft Access setup program.”

Uninstalling and reinstalling is of no help. Can anyone give me some advice on how to get Access 97 working on this computer?

Mike

[Geekgirl]

This is the only thing I could find

Just copy the default workgroup file from any system with 97 installed. The problem though is a bit unusual, are you sure that you have full administration rights on the account you are using? The inability to access system32 suggests that you do not. If this is the case, log in as the administrator and run the install again. The “changing workgroup database” error also implies that another version of Office/Access has been installed previously. Access will have issues if O2000 has been removed then O97 is installed. In this case, it is necessary to rename the hatten.ttf font to hatten.old, run the install again, then rename the font back as it was. (A classic Windows bug from a few years back...)

http://www.helpscreen.com.au/index.php?msgid=934243871&cid=9