Here's the scenerio: Access database I developed when I had Office Pro 2002. My machine has been upgraded and IM department installed Outlook 2003 and retained the rest of Office 2002. Now, when people enter the same database they have been using without a problem before, they receive the error message "Problem loading DLL" or something similar. This distresses me slightly because I don't know how to trap that error and the user is thus introduced to the VBA editor in debug mode! I have managed to find a quick and dirty fix which is highly similistic, but works: copy the Outlook 11.0 Object Library file (MSOUTL.OLB) from my computer and create a new folder called Office11 alongside their Office10 folder in Program Files > Microsoft Office and pop the MSOUTL.OLB file in there. There has been 100% success using this tactic, but I am not satisfied:
Did Access automatically update the Outlook 10.0 Objects Library that I must have checked when developing to Outlook 11.0?
If so, would this have happened when I open the database? or will it be some kind of roll-out thing I should know about?
What would be a more suitable, long-term, sure-fast fix for this problem?
How can I trap this error in the future?
By the way, I no longer have the Outlook 10.0 Objects Library available in the list.
Your expert opinions are much appreciated on this issue.