Now still using Access 2003, too lazy no way, up to 2010 changes too big, make a transfer version of Access is very troublesome. Besides, we are all using 2003, and we are too lazy to engage in it.
The problem is that Office 2003 is out, and (Office 2003 retired on April 8, 2014). You must use the new version of Word and Excel. Some colleagues in the company will use other methods such as WPS, converter and so on.
Today, a colleague opened the 2003 version of the MDB found that open xx window error, what loading errors and so on. began to think that the Office update is bad, so reload Access2003, error is still. Later the new and Old MDB window to change, or not, but there are DLL loading errors, there is a puzzling engineering errors, compile errors or something. Online check to find out, try to try, engaged in a chase or not.
Finally, I finally found out why. In VBA there, the ' References ' dialog box has a ' mircorsoft word 14.0 ' display missing in the faulty machine, and the OK machine is no problem. Do not reference it, problem solved! But the reference is necessary, and some functions depend on him, so they try again and again. Originally, ' quote ' to find a lower version of the machine to do (a colleague and Word v11, the reference is finished, the MDB has unknowingly saved the ' reference ' changes. Word is a high-version machine that can be backwards compatible.
Because there are two versions of Office installed at the same time, compatibility issues between versions are more complex. If you use a machine with a high version of Word, and you have it to modify the version 2003 access, unknowingly, some of the connections to access (such as the ' reference ' for this discovery) will be saved, and the lower version of the machine will encounter problems when it opens the MDB.
It's time to consider abandoning the access2003.
Ps
Office V11 =2003
v12=2007
V13=?
v14=2010
v15=2013
ACCESS DLL Loading error