General Question Over Ms Access Reference Libraries, Runtime, and the Such in VBA

I have Access 2016 on some systems and I don't have any Office on some other systems. I am currently using Dymos SDK which uses different references that were installed in Access during the SDK install. My main questions is....When you develop a Front End in Access 2016 with these references and then run them on another PC with Runtime only.  Are the references embed in the Front End and will it still work?

I have had some bugs while running in runtime and in the next few days I am going to try and smooth out the system. It worked perfect on my PC with 2016 where it was developed. I just want to clarify this first. Thanks!
LVL 1
Dustin StanleyEntrepreneurAsked:
Who is Participating?
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Connect With a Mentor Infotrakker SoftwareCommented:
No, they are not embedded. You must deploy and install any non-native references used in your project. In the case of your SDK, you'd have to determine exactly what files are required for "runtime" and deploy/install those. You may also need other objects with that Dymo feature (the "label" file, if you used one).

You should do this with an installer of some sort. The deployment mechanism in Access is pretty lame, but you could try it to see if it works. You'd be much better off using a commercial installer like InstallShield, Inno Setup, Installmate, etc. One of the most important things an installer does is ensure your target environment has all required files and libraries. It also allows you to easily deploy and install/register items like your Dymo SDK.

If you want to try the built in process see this article for more information:

https://support.office.com/en-us/article/Create-an-Access-app-package-5c409c03-ded9-4a41-82c3-fdd490a91b42?ui=en-US&rs=en-US&ad=US&fromAR=1

I also note you will be deploying to users without Office. If you have a reference to any of the Office libraries other than the Office 16.0 Access database engine Objects, your application will fail. For example, if you're using Excel or Word automation then your end users would be required to have a licensed copy of Office on the machine.

You should also thoroughly test your application in Runtime mode, since it seems you'll be deploying to users without Access installed (or Office, for that matter). You can do that by saving a copy of your application with the .accdr extension, and then run that copy. Access will simulate the Runtime environment.

You should also run a split configuration, where you're supplying a BackEnd (Tables only) and a FrontEnd (everything else). This will require you to have some form of "relink" code, so be aware of that.
1
 
Dustin StanleyEntrepreneurAuthor Commented:
Thanks!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.