Disclaimer: I just got back from some sick time, haven't seen the error myself or investigated the full range of possible causes, just looking for hints on what may be a systemic issue or something others have experienced in a similar situation.
Migrating the office to Office 2010 from Office 2003. Several critical Access Databases now give errors when opened in 2003 similar to what you'd get when you're using libraries you haven't set up properly in References (VBA app: Tools => References).
I'm investigating to see if the issue occurs when the files are opened in Access 2010 the same as when opened in 2003. Also, I'm trying to get a comparison to which libraries are referenced on machines that are working versus those that aren't. I'll update as I have more information.
In the meantime, is anybody aware of similar issues that may be addressed by a configuration change rather than a MDB edit?
Libraries referenced in 2010 system where MDB works:
- Visual Basic for Applications
- Microsoft Access 14.0 Object Library
- OLE Automation
- Microsoft ActiveX Data Objects 2.1 Library
The second library brings a question. The MDBs were originally written probably using Access 97, otherwise, using Access 2003, and so would have referenced the appropriate "Microsoft Access 12.0 Object Library" (for 2003) or similar. Will opening the file in 2010, as we see it's modified this reference to the 14.0 version, cause 2003 to look for that same version 14.0 library?
UPDATE: I've checked MDB files on my system, which does not appear to be having the issues (of course). The referenced libraries are the same in both Access 2003 and 2010 and the Microsoft Access ##.# Object Library reports 11.0 in 2003 and 14.0 in 2010, which should indicate it is not "hard set" in the code.
I will check the security options suggested by the commentor below and report back.