MS Access 11.0 Object library

[rodmc]

OK, I got Access 2007 forced on me recently, IT updated but I couldnt make changes to my 2k3 files (.mdb) without a massive headache, SO after much fighting I eventually got them to install 2k3 again.

The problem I have is that the system IM working on keeps telling there is missing references, so in other words no buttons work.

So I checked the references, my older system was using 11.0 Object Library, but the latest installed version is 12.0. Im thinking this is the problem, can anyone confirm that this would cause these problems?

 

[Trevor G]

When you checked your references did it show you the word MISSING in front of anything at the top of the list of refences, if so then you would have to remove the tick and search down the list for which version you have on your machine.

Alternatively have you had any Add Ins removed?

 

[rodmc]

Hi Trevor

there are no missing references, and I had no add ins, the only change I can see is the change from 11.0 to 12.0.

I should also explain that I still have 2007 installed

cheers

rodmc

 

[boblarson]

If you open the Access file from Access 2007 it will upgrade the reference automatically from 11.0 to 12.0. But, if you then go back and open it with 2003, it will show a reference error and you will have to go into the references and change it back from 12.0 to 11.0.

 

[Trevor G]

12 is 2007 so that shouldn't be the issue. Try this. Select the Office Button at the top left then Options at the bottom then Trust Centre, then on the right Trust Centre Settings and then select the Macro Settings and ensure the bottom option has been selected. Enable all Macros.

 

[boblarson]

And additional - if you are using any DAO, the reference could have changed to ACE from DAO and that may also need to be set back to Microsoft DAO 3.6 from the Microsoft Office Access Engine 12.0 Object Library.

 

[rodmc]

Well, fortunately I have another PC at my desk (2 different networks) one was untouched, the system works fine there, so I can transfer back to the server from there and the end users do not have 2007, so one positive from this debacle

They installed both versions to the same folder on my laptop though, Why in gods name did they not create an new folder in Program files so that they had there own dll's and such.

Anyway thanks guys, your help and advice, it is much appreciated, I'll need to set about the office installs tomorrow and get it sorted, nightmare!

 

[Pat Hartman]

1. What exactly was your problem with using A2007 to update the .mdb's? You should not have had any problems.
2. Microsoft's children do not play well together and different versions of Access will fight constantly over control of the registry so you have to be very aware of what is going on to keep out of trouble. One solution that worked well for me was to create shortcuts to each version and specify that they execute with Admin permission. In Vista (which is what I was running when I had the problem), if the app isn't running with admin permission, the registry take over is incomplete and the strangest things happen - this may be what you experienced. To use this method, click on the shortcut and choose the database you want to open. I'm assuming you are a developer and so work with many apps that are not yours. If you use only a couple of apps, you could make the shortcuts, open specific databases forcing the use of a specific version as long as they operate as Admin, they will be fine.
3. Uninstall A2003 - you may have to uninstall A2007 and reinstall it also and you should be able to use A2007 to update your A2003 databases without any problems.

Why, I might add, would a company upgrade to Office 2007 at this point? A2010 is out and stable and a new version will be released in the spring. Why go through the pain of upgrading to still be behind especially when Office 2010 fixed a lot of the "first" version issues with the ribbon and nav pain (sic)?