We have a master copy of an Access 2010 database on a network that is automatically downloaded to the user's machine whenever a change is made. On the master version, there is a reference to the Microsoft Office 15.0 Object Library. This works with all the user's machines except for one. There is one person who does not have the 15.0 library, they have the 14.0, so everytime they download a new copy, they get a missing reference error.This is easy enough to fix manually, you just go in and change the reference to 14.0 but we do regular updates, so having to constantly going to their machine and making the fix is not an option.I've googled and googled trying to find something on how to resolve this but to no avail. Any assistance would be appreciated.P.S. I was thinking about just copying the dll for the 15.0 from my system 32 folder and placing it in theirs but thinking that probably wouldn't work but if it would, does anyone happen to know the name of the Microsoft Office 15.0 Object Library dll?
- Download Microsoft Excel 15.0 Object Library Dll
- Install Microsoft Excel 15.0 Object Library File
- Install Microsoft Excel 15.0 Object Library Download
Doug,We're all using Office 2010 and 15.0 is what we all have except for the one machine. The only option I have is for 15.0. I read up briefly on Microsoft Office Primary Interop Assemblies.
I know that is installed. Would that have anything to do with changing the reference version? The object version is not directly tied to a Access. For example, if someone had Microsoft Outlook 365 and Access 2010, installed on the same machine, the Outlook references would be for the 365 version.Are you familiar with the Interop Assemblies and know if that would change the version numbers?
Download Microsoft Excel 15.0 Object Library Dll
If so, maybe, just installing it on that user's machine would correct the problem. We all have Office 2010, I'm positive of that. I'm thinking that the Interop installation had something to do with why it's 15.0.
Install Microsoft Excel 15.0 Object Library File
If I change the reference to that location to get 14.0, is that going to work on everyone else's machines when they download a new version? I'm thinking that's probably not going to work especially for the person who does not have the 15.0 because their dll is located in the system 32 folder but I could be wrong, which I hope I am.Thanks for the link, Doug.
I couldn't find anything in that. If that person has office 14, and it's been installed in the standard location, then it will be where I said it was a few posts back.C:Program Files (x86)Common Filesmicrosoft sharedOFFICE14mso.dllSo if it's in the same place for everyone, then it's going to work.Otherwise, as cheekybuddha has supported my other two points, Are you actually using anything from that object library? (and I said how to check)or late bindingI'm assuming that the 'one person' doesn't have a weird one off machine set up. As I said earlier, it's easy to fix manually, I just change the reference to 14.0. We don't necessarily need 15.0, it's the dll that is on every other computer except the one person whose latest and greatest is 14.0. They do not have a different OS, different Office version, everything is exactly the same on all machines.
That's why more and more I'm thinking that the Interop Assemblie is responsible for placing 15.0 in place of 14.0.I'm going to try your suggestion, so thanks for that but I think for the long-term fix, I'm going to try installing the Interop Assemblie on their machine and see if that does the trick. Since everyone already has 15.0 versions, I'd prefer that we're all on the same, so down the road, won't have to worry about running into this issue again.Thanks all for the help. Doug, I believe it's going to work but by default, doesen't Access use the dlls that are in the System 32 folder? My concern with that is down the road if we end up using references to other objects and they are 15.0 e.g. Microsoft Excel 15.0 Object, Word, etc. Then we're going to need to make sure that we point the reference to the Office 14 folder each time.I'm just a stickler for consistency where everyone is using the same versions as much as possible, so doing tasks like upgrades and changes are straight-forward without the need for any tweaks.I do appreciate all the insight though and I am going with the fix that dmhzx suggested. Thanks again.
Just want to clear up a few things.Its not a '2010' database.Access databases are really only either.mdb format or.accdb format (runtime versions as offshoots of these).Your.accdb can have references to Office/Access 2007 up to 2016, it might also have some objects that are only available in a higher version, for example empty cells in a form layout (added in a later release) cannot work in 2007 and will crash Access. The database opens and runs fine as long as you dont go to that specific form.Your database has references to 2013 so really needs to be opened on machines with that or higher.Now your current setup sounds wrong. Machines with 2010 on it should have references to 14.0 as indicated. We have a master copy of an Access 2010 database on a network that is automatically downloaded to the user's machine whenever a change is made. On the master version, there is a reference to the Microsoft Office 15.0 Object Library.
Install Microsoft Excel 15.0 Object Library Download
This works with all the user's machines except for one. There is one person who does not have the 15.0 library, they have the 14.0, so everytime they download a new copy, they get a missing reference error.I expect a user is trying to use the master database directly, causing the references to change, rather than just copy it to their own folder. I assume you issue this with the references to 14.0. Check the date, and you will probably see the date change from when you released it. You could add a table to record the windows name of anyone who opens the master database. It might be useful.
. Post titles to your problem.
Provide in your post. Use the for non-questions. Only text posts are accepted; you can have images in Text posts.FAQ.Was your problem solved?OPs can (and should) reply to any solutions with:This will award the user a and change the post's flair to solved.
To apply code formatting Use 4 spaces to start each lineYou can select code in your VBA window, press Tab, then copy and paste into your post or comment. Provide your dataInclude a or use the website to generate the reddit table markup from your spreadsheet.Congratulations and thank you to these contributors DateUserCP251025A community since March 11, 2009 Download the official to convert Excel cells into a table that can be posted using reddit's.