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.
LVL 1
mlcktmguyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

John TsioumprisSoftware & Systems EngineerCommented:
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.
NorieAnalyst Assistant Commented:
Is it actually 'MSOUTL.OLB'?

If it is then its probably a reference to the MS Outlook library.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Fabrice LambertConsultingCommented:
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.
mlcktmguyAuthor Commented:
Thanks you.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.