I recently installed Office 2003 Pro (incl the Office SP2 update) on a new computer and moved my data to this computer. Both the old and new computer are WinXP Pro + SP2.
Other Office apps (Word, Excel, etc) seem to be running fine, but whenever I attempt to open one any of several .mdf files (all of which I created) Access tries to install DAO. It looks for dao.msi in a temp folder and can't find it, rolls back the DAO install resulting in a dysfunctional DBMS.
I've done the following:
1. Run a Windows search (incl hidden/system files) for dao.msi on both of my hard drives and on the Office installation CD - not found.
2. Tried both Detect and Repair, and then a full uninstall/reinstall of Office 2003 - no change.
If I click the cancel button, the DAO again attempts to install, and after cancelling a few times, the message goes away and I get into the database. From there it seems to be working OK, although I don't know if there is something lurking around that will bite me later. Either way, having to go through this process every time I open the .mdf file is pretty annoying.
The .mdf files were originally created in Access 2002/XP and I seem to recall solving this same problem when I first installed Office 2003 on my older computer, about a year ago, but don't recall how I did it.
All suggestions are appreciated.
Thanks,
Phil
Other Office apps (Word, Excel, etc) seem to be running fine, but whenever I attempt to open one any of several .mdf files (all of which I created) Access tries to install DAO. It looks for dao.msi in a temp folder and can't find it, rolls back the DAO install resulting in a dysfunctional DBMS.
I've done the following:
1. Run a Windows search (incl hidden/system files) for dao.msi on both of my hard drives and on the Office installation CD - not found.
2. Tried both Detect and Repair, and then a full uninstall/reinstall of Office 2003 - no change.
If I click the cancel button, the DAO again attempts to install, and after cancelling a few times, the message goes away and I get into the database. From there it seems to be working OK, although I don't know if there is something lurking around that will bite me later. Either way, having to go through this process every time I open the .mdf file is pretty annoying.
The .mdf files were originally created in Access 2002/XP and I seem to recall solving this same problem when I first installed Office 2003 on my older computer, about a year ago, but don't recall how I did it.
All suggestions are appreciated.
Thanks,
Phil