Avatar of mlcktmguy
mlcktmguy
Flag 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. Reference Error Message
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.
Microsoft Access

Avatar of undefined
Last Comment
mlcktmguy

8/22/2022 - Mon
John Tsioumpris

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.
ASKER CERTIFIED SOLUTION
Norie

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Fabrice Lambert

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.

Solution:
Review the source code and switch to late binding.
mlcktmguy

ASKER
Thanks you.
Your help has saved me hundreds of hours of internet surfing.
fblack61