Link to home
Start Free TrialLog in
Avatar of mlcktmguy
mlcktmguyFlag for United States of America

asked on

Access 2013 Application message, Searching for Reference HSOUTLOLB?

A client recently reported getting this message as they try to print from a Access 2013 application I installed for them.  The message come up when they are trying to print a client account statement from the application.

Background: This application has been installed and running without issue for over a year.  I have made no application changes in that time period.  They just started getting the missing reference message last week. They sent me a snapshot of the message. User generated image
It look like 'HSOUTLOLB' but I did a search on that and nothing came up.  

My first thought is that they changed something in their operating envioronment but I just wondered if any EE'ers might have a better knowledge of what might cause this issue.
Avatar of John Tsioumpris
John Tsioumpris
Flag of Greece image

HSOUTLOLB seems like a custom made "object" (dll,ocx,mde...etc) that is referenced and now it has issue...You certainly should take a look a references and i *guessing* that seems like a a "bridge" component to their ERP.
Avatar of Norie

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
With some (bad) luck, the application has an early bound reference to Outlook, and your client opened the application from a computer with an upgraded version of Outlook (upgrading the reference in the process), then ran it on a computer with an old outlook version.
The upgraded reference does not like the old Outlook and report itself as broken.

Review the source code and switch to late binding.
Avatar of mlcktmguy


Thanks you.