Object Libraries 2013 and 2007 Compatibility

[tdefreest]

Hello,

I recently upgraded my system to Office 2013 and the Object Libraries have automatically been up-scaled to 15.0 in the database.

The problem: some of the end users in my department are still running Office 2007 and their machines are not compatible with Object Libraries 15.0 and can only run 12.0 (I believe).

My question: Is there a way to dynamically set Object Libraries using a few lines of code that I can insert? Or: is there a way I can set the database to ignore the request to upscale the Object Libraries to 15.0?

Unfortunately, search results did not yield anything for this issue.

Please help! Many thanks in advance for your consideration.
-Tim

 

[The_Doc_Man]

Of greater interest - For Office 2007, everything was 32-bit. For Office 2013, you have a choice of 32-bit or 64-bit formats. The libraries are NOT compatible because you have to worry about "address safe" extensions for a lot of the more common routines. It is a problem not because of machines being incompatible, but because of a choice that was made when you upgraded to Office 2013. And the worst part is that if you weren't aware of the implications, you might have just blown past the option completely.

On Access 2013, open your database. Select File (tab) >> Account (in left-hand panel) >> About Access (near center of screen). The top line of the resulting dialog box will tell you whether you are on the 32-bit or 64-bit version.

If you were to remove the 64-bit version and reinstall Office as a 32-bit version, your issues of compatibilities would mostly go away, I think. We have an app that was originally developed under Office 2003 (in part) and is now on Office 2013 (32-bit). We had to change maybe two or three functions to make it work.

The stalling point would be if you are using SharePoint in Office 2013, you might not be able to step down to 32-bit calls. Otherwise, you should be OK.

 

[tdefreest]

Thank you The_Doc_Man. I have checked this and can confirm I am running 32-bit.

More information, this code I am running automatically has the user to open both Outlook and Excel to draft an email and create a pre-populated excel template. Maybe has something to do with it?

Object Libraries referenced are:
Visual Basic for Applications
OLE Automatic
Microsoft ActiveX Data Objects (Multi-Dimensional) 6.0 Library
Microsoft ActiveX Data Objects 6.1 Library
Microsoft Access 15.0 Object Library
Microsoft Access 1.0 Access database engine Object Library
Microsoft Office 15.0 Object Library
Microsoft Excel 15.0 Object Library
Microsoft Outlook 15.0 Object Library


Before I upgraded to 2013, all of these were 12.0 Object Libraries.

Edit: I was able to resolve the issue by convincing our IT department to upgrade the rest of the users to Office 2013.