I have a long-established MS Access project that's linked to a remote SQL server installation. A recent system crash on my main development PC forced me to do a system restoration and to reinstall Access. Since then, I've been unable to open this project (.ADP file) from this machine. I can open the project from other machines on my office network; an Access database (.MDB file) that's linked to the SQL server via ODBC is properly connected and functioning correctly on all machines. Also, a series of .ASP web pages are working correctly using ADO connections to the underlying SQL database. And a separate
Access project that is linked to the same SQL server is behaving the same way: "disconnected" on my PC, opening normally on other PCs, correctly driving .ASP pages on the website.
When I attempt to open the file, Access returns an empty window with the heading "[filename] (disconnected) :Database"
The machine in question is running Windows XP Pro SP 3; Access 2000 9.0.6926 SP3. This was a new installation directly off the MS Access install disk.
I have confirmed that I have MDAC 2.81.1132 installed.
The other machines from which I'm able to directly connect are running XP Home, Access 2000 version 9.0.2720, and MDAC 2.81.1132. I admit I'm a little puzzled at the difference in Access versions because all of these were installed from the same disk.
I've attempted several uninstall/reinstall cycles with Access, and also installed the XP Pro Service Pack 3, after restoring my system. (This is one of those HP recovery-partition boxes that came without Windows disks.) Because I was able to connect to this project before having to partially reconfigure my system, and because it's working correctly on other PCs, this is clearly a matter of some quirk or tweak or missing DLL in Access or Windows. But I can't find any reference to help me figure out what it is.
There was a closely related thread from 2006 that unfortunately didn't offer any solutions: