MS Access "can't perform this operation" error removing object library
Very frustrating. I have an MS Access database application that I have connected w/ SQL Server.
It has worked fine but now the Word, Outlook and Office changed from 14 to 15 in the object library. I guess that's because I opened it with my laptop which has Office 2013 (I have 2010).
I can't get it to go back.
I changed the Word and Office library to 14, but then I noticed i didn't move the Outlook back. It shows as missing.
I can't drop it. When i uncheck it and close it gives me an error saying "can't perform this ooperation". I try every combination of dropping the three libraries but no luck.
What am I missing?
It has worked fine but now the Word, Outlook and Office changed from 14 to 15 in the object library. I guess that's because I opened it with my laptop which has Office 2013 (I have 2010).
I can't get it to go back.
I changed the Word and Office library to 14, but then I noticed i didn't move the Outlook back. It shows as missing.
I can't drop it. When i uncheck it and close it gives me an error saying "can't perform this ooperation". I try every combination of dropping the three libraries but no luck.
What am I missing?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks. I can't believe i didn't think of opening it up on my laptop.
Over the years I have had to wrestle with the issue, but it was never a problem before just unchecking the MISSING references and then opening the older versions.. that threw me off.
I looked at the article and it seems like the late binding isn't a perfect fix. The client office is all on the same version at the moment. I'm the one with the new Windows 8.1 laptop that is screwing things up.
Thanks again.
Over the years I have had to wrestle with the issue, but it was never a problem before just unchecking the MISSING references and then opening the older versions.. that threw me off.
I looked at the article and it seems like the late binding isn't a perfect fix. The client office is all on the same version at the moment. I'm the one with the new Windows 8.1 laptop that is screwing things up.
Thanks again.
I looked at the article and it seems like the late binding isn't a perfect fix.
I use later binding all the time to support mixed versions of Office without any issues I even have used with mixed versions of Office apps on the same PC. Later binding has been the "perfect fix" for me for 1000+ users.
Go into references *on that laptop* and remove the Outlook reference
Then try it again on an Office 2010 machine, adding Outlook in as a new reference.
(not sure why, but those Outlook references seem to behave a little differently)