How fix references for a computer having only ms/access runtime?

 I need to deploy my app to additional computers having only ms/access runtime. How fo I fx the references?
João serras-pereiraAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Bill PrewIT / Software Engineering ConsultantCommented:
Need more information, what references are you having problems with?  What errors are you receiving?

João serras-pereiraAuthor Commented:
Ok. I'll new a few hours to get it as the target computer is on 4,500 Km away(...) I'll get the screenshots and will come back.
Anyway, in more detail, what is happening is that, on my development computer, everything is right. As I am using third party controls, I installed them on the computer.

But the software just crashes without telling where. The target computer has no Office but only ms/access 2016 runtime, so I am blind to debugging there.

As soon as I have the screenshots, (hopefully in a few hours) I'll come back to the question
Only use late binding.  No references.
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
As aikimark said, Late Binding can be the solution here. However, if you're using the Office Objects reference, then the target computer MUST have Microsoft Office installed. That's the only way to get that reference. You cannot deploy it legally, and even if you could you'd have to deploy a host of other libraries to support it.

You can post a screenshot of the references on your machine, and we could tell you which ones will potentially give you troubles.

But the software just crashes without telling where.
This often means you don't have error handling in place. Each code routine must have full error handling in place, otherwise you risk an abrupt end (i.e. a crash with no information). MZ Tools is a great way to quickly add error handling to all your routines. It's no longer free, but it's well worth the money:

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
João serras-pereiraAuthor Commented:
Hi Thanks a lot! references are (for the moment), solved; the end computer will be a runtime only, but I have installed (legally) Office and could manage the errors in a better way
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.