Member Avatar for Thermalnuke

Hey guys Im doing some testing on a few database conversions from MDB format to accdb. I packged up my files so when the exe was ran it would install MS runtime as well as the databases needed for the app. I was trying to get it so that I wouldnt have to install MS office access on the client machine. I just wanted to run runtime so the client machine can still access the database/ forms. After installing my package i ran the desktop app and it booted up to an error saying a missing DLL was the conflict then it would just crash all together....so i went back to the original database and look of the refrences under VB and saw the DLL, i decided to un-check the DLL and and re run the database and it work, so I re packaged everthing and re-installed and it just instantly crashes now.

so in conclusion. Im wondering if it would just be easier to just install MS office access. Im starting to think that you DO need MS office to even use runtime correctly. if this is the case then i will install office, but i was trying to run the forms to the database so i wouldnt have to get keys or even purchase multiple copies of MS office. any thoughts on this would be excellent or if im doing something wrong with the testing or a step im missing please let me know.

but my conclusion is i need to install MS office access to run MS runtime.

-Thermalnuke

  • 1 Contributor
  • 2 Replies
  • 308 Views
  • 33 Minutes Discussion Span
  • Latest Post Latest Post by Thermalnuke

Dani AI

Generated

— short answer: you do not need full Access installed to run an Access runtime application. The Runtime is a freely redistributable package, but it only includes the runtime engine and common data drivers — any extra COM/ActiveX controls, third‑party DLLs or mismatched Office libraries your front end references must be present and correctly registered on the client. (support.microsoft.com)

A "missing DLL" / "MISSING:" reference in VBA is a classic cause of the behavior you describe: clearing the reference hides the dialog but will not stop runtime crashes if code still calls types or functions from that library. The normal dev workflow is to open the VBA editor (Tools → References) on the development machine, note any MISSING items, and either restore/register the missing file on the client or remove/replace those calls (late binding is a common fix). In runtime you cannot view the References dialog, so you must diagnose and fix references on a build machine. (learn.microsoft.com)

Practical checklist of the most common deployment causes and fixes:

  • Third‑party OCX/DLL not present or not registered on the client — register with regsvr32 (use the SysWOW64 regsvr32 for 32‑bit controls on 64‑bit Windows).
  • Bitness mismatch: 32‑bit Access/Runtime requires 32‑bit controls and providers; same for 64‑bit. Choose the correct runtime/engine.
  • ACCDB needs the ACE/Access Database Engine components if you rely on OLEDB/ODBC/DAO providers. Include the correct redistributable and match bitness when packaging. (support.microsoft.com)

Quick steps to reproduce and eliminate the problem:

  1. Install the same Access Runtime on a clean VM (no full Access).
  2. Open the DB on your dev PC, note MISSING references and replace with supported libraries or convert to late binding where practical. (codestack.net)
  3. Make an ACCDE, include and register any OCX/DLLs in your installer (or instruct users to install the Access Database Engine), and add basic startup logging or write exceptions to a log file so you capture the exact failure point. Use the regsvr32 form below when manual registration is needed:
%systemroot%\System32\regsvr32 "C:\Path\To\control.dll"
%systemroot%\SysWOW64\regsvr32 "C:\Path\To\32bit-control.ocx"

If the app runs under full Access but fails under runtime, that strongly indicates a missing or unregistered dependency (not a licensing requirement). Address those dependencies and the runtime deployment will work. (microsoft.com)

Member Avatar for Thermalnuke

BTW Un-checking the refreance and packageing it back up did solve the missing DLL box that came up, it just goes directly to crashing just wanted to clarify, but when i run the app on a computer with microsoft office access it runs perfectly in runtime

Edited by Thermalnuke
Member Avatar for Thermalnuke

might be a licence issue?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.