Reference for Access 2002

We have a machine with both Access 2002 and 2010 on it. The user uses two dbs built in 2002 along some vba code. When they are started the code breaks. When I go into references, it shows MS Access 14 is checked off but no reference to MS Access 10. When I navigate to msaccess.olb for 10 I can find it but cannot add it to the reference list.

Popular White Paper On This Topic

You may want to try leaving both references out and adding the correct one through code based on the version, or checking to see if the correct reference is there and then, if not, removing the wrong one and adding the correct one. Essentially, the code is Access.References.AddFromFile "path_to_reference" where path_to_reference is the full path to the file.
You can google how to do this (check out this link: http://www.access-programmers.co.uk/forums/showthread.php?s=5c4b381d 0cddf4fe4ebca5ec9be3c251&t=185352") This will work for some references, but not those required to initiate the app.

It is not that they cannot both exist on the same machine.. It is that only one object library can be referenced by either at one time. Unfortunately and to add to the difficulties, by default, both forms of access will only be able to use the most recent object libraries available because, on installation, the relevant keys in the registry are managed on the basis that the most recent object library must work and therefore there is no need to install an earlier library.

The issue then is that because there are changes in object properties and if you have an early version of access trying to use a later version of an object library, occasionally, properties and methods passed from the older Access to the newer library may miss out method parameters/properties the newer library needs? And so on. The reverse applies if you use a newer version of Access with an older object library.

In other words, you are likely to have problems no matter what you try to do. Use two machines?.

From our experience, this isn't a problem with Access 2010 and 2007 on the same machine. And I think Access 2003 may be okay, but Access 2002 definitely causes databases to reference one Access object and not be able to change regardless of which version of Access was last launched.

1-Get a Virtual environment (VmWare is a solid program)
2-Install Access 2002 in point 1
3-Uninstall Access 2002 from normal environment
3-Any change to Access 2002 you must do in virtual environment
4-Changes to Access 2010 you do it as usual.

Access has a problem, if you install upper version any time you do a change to a Database, Access add new features so lower versions of Access
can not recognize.

Reply from LukeChung-FMS on Jan 16 at 5:21 PM Access 2002 and Access 2010 can't be on the same machine if you want to use VBA modules. You're encountering the exact conflict that prevents the two from working properly.

For example, in the Target section of the shortcut Properties, enter text that is similar to the following path for Access 2003:
"C:\Program Files\Microsoft Office\Office11\msaccess.exe" "C:\My Documents\mymdb.mdb"
For Access 2007, the path resembles the following:
"C:\Program Files\Microsoft Office\Office12\msaccess.exe" "C:\My Documents\mymdb.aacdb"

This article points towards a 2002 version where the following is suggested:
If neither of these methods resolves the issue, you must manually create a new shortcut. You must include the path to the correct version of Msaccess.exe and the path and file name of the database that you want to open. For example, in the Target section of the shortcut properties, enter something similar to the following:
"C:\Program Files\Microsoft Office\Office10\msaccess.exe" "C:\My Documents\mymdb.mdb"

Keep the references in each database correct for the version which is being used.

The issue here isn't how to startup the right version of Access. It's that even if you manually launch the right version, Access 2002 won't perform properly if Access 2010 is installed on the same machine. Same thing applies to Access 2007 if Visio 2010 is installed on the machine (without Access 2010 also installed).