Microsoft Access Runtime

I thought I’d take a second to explain what Microsoft Access Runtime is, and is not.

What is Microsoft Access Runtime?

In the simplest terms, Microsoft Access Runtime is a stripped down version of Access in which the developer/design tools have been removed/disabled, including VBA tools. So you can run existing databases, run their code, …, but any ability to edit them (objects or code), create new objects, etc is disabled or removed.

I also want to be 100% clear here, runtime locks down editing the database objects and code, not the data itself.  So in runtime, users can still fully work with the data as you have allowed them to do (full CRUD).  It just limits their ability to alter the actual “program”.

The primary purpose of the Microsoft Access Runtime version/edition is to enable people who don’t already have Microsoft Access installed to get a free version that allows them to fully work with any existing Microsoft Access database or in some instances it is a means to restrict the end-users abilities to edit the database (even if they already had the full version of Access)

What is Microsoft Access Runtime Used For?

As mentioned above, Microsoft Access Runtime is typically installed for users that do not already have a Full licensed version of Access.  So long as your user does not need to create and/or edit database objects such as: Forms, Report, VBA code, … then the FREE Microsoft Access Runtime will be perfect for them and allow them to run and use any existing database.

So with Microsoft Access Runtime you can fully utilize any existing database solutions, you simply can’t develop them!  You can still use forms, reports, execute the macros & code contained within, you just can go into design view, enter the VBA Editor (VBE), …

So Runtime allows you to distribute your database to user that do not already have Microsoft Access at absolutely no cost!  Since Office 2007, Microsoft Access Runtime is Free.

Something To Consider
Some developers will actually install the runtime version, regardless of whether or not their users already have the full version of Access installed, because it adds an additional layer of security to their databases and restricts what their users can change.

What Microsoft Access Runtime Is Not?

As previously mentioned, Microsoft Access Runtime is not a development tool.  Developers still require the Full version of Microsoft Access to be able to create/edit database objects.

An analogy might be imagining Runtime as a car.  You can drive around town all you want and use it, but if you want soup up your car you still need to visit a mechanic with all their tools (Access Full version).

Where Can You Get Microsoft Access Runtime?

Below are links to Microsoft’s Runtime downloads.

Here are the Way Back links as the original URLs disappear!

Microsoft Access 2007 Runtime
Microsoft Access 2010 Runtime
Microsoft Access 2013 Runtime
Microsoft Access 2016 Runtime
Microsoft 365 Runtime (use this for 2019, 2021, … and MS365)

Here are the original URLS

http://www.microsoft.com/en-ca/download/details.aspx?id=4438 -> Microsoft Access 2007 Runtime
https://www.microsoft.com/en-ca/download/details.aspx?id=10910 -> Microsoft Access 2010 Runtime
https://www.microsoft.com/en-ca/download/details.aspx?id=39358 -> Microsoft Access 2013 Runtime
https://www.microsoft.com/en-us/download/details.aspx?id=50040 -> Microsoft Access 2016 Runtime
https://support.microsoft.com/en-us/office/download-and-install-microsoft-365-access-runtime-185c5a32-8ba9-491e-ac76-91cbe3ea09c9 -> Microsoft 365 Runtime (use this for 2019, 2021, … and MS365)

Things To Be Aware of With Microsoft Access Runtime!

Since, all development tools have been removed/disabled,

  1. You cannot debug any VBA errors, thus it is critical to add error handling to all your VBA procedures otherwise when an error occurs the database will crash
  2. You do not have access to any of the option menus, so you need to find an alternate method to
    1. Set general database properties (startup form, title, …)
    2. Create Trusted Locations to enable the VBA code within your database (this can be done with VBScripts)
  3. Tools like the Linked Table Manager are not accessible, so you need to implement an alternative
  4. There is currently no Runtime version for Click-To-Run editions of Office 365.  It is only available/compatible with MSI versions of Office.  That said, Microsoft now include Access with all Office365 editions, so all Office365 user should already have access to Access, no need for the Runtime version for them.

From Microsoft, below is a list of the feature which are removed from Microsoft Access Runtime.

The following features are not included as part of the Access 2007 Runtime without additional customization:

  • Navigation Pane
  • Title bar text/icon (can be specified by the database instead of by Access)
  • Default Office Fluent Ribbon
  • Quick Access Toolbar
  • Shortcut menus
  • Access Help
  • Designers (including Filter by Form)
  • Visual Basic EditorMicrosoft

Simulating Runtime

As a developer running the Full version of Access we sometimes need to test how our application will behave in the runtime environment.  Now in an ideal world you would build a Virtual Machine (VM) that has the runtime version installed.  That said, Access does have a command line switch that can be employed with the full version to simulate the runtime environment.  So you can use the /runtime command line switch as part of your call to open a database and see exactly how you database will look and behave in the runtime version of Access.

So you would use a command similar to the following in a command prompt, bat file, vbscript, …

“C:\FullPathTo\msaccess.exe” “C:\FullPathTo\Database.mdb” /runtime

This is also where my Context Menu can truly help developer.  To find out more, take a look at my post:

Windows Explorer MS Access Database Right-Click Context Menu
I was part of a discussion, Easy Use Command Switches \decompile \excl \compact \runtime Etc, Access 2010 , regarding Windows Explorer Context Menus for sending/opening accdb files to: Compact Decompile Runtime Up until now, I simply created a couple of shortcuts with I added to the SendTo Menu as described in the Reusable decompilation method…

Continue reading →

 

Another option is to change the extension of your database file from *.accdb to *.accdr which makes Access run the database simulating runtime.

Windows S Systems!

Just a quick word regarding Windows S systems and Microsoft Access and/or Microsoft Access Runtime.

There is currently no version of Microsoft Access and/or Microsoft Access Runtime that will install/run on a Windows S system as there is no Microsoft Access or Microsoft Access Runtime app in the Microsoft App Store!  So you’ll need a system running plain Windows or you’ll need to switch your Windows S mode PC over to standard Windows mode to be able to install Microsoft Access or Microsoft Access Runtime.

More Resources on the Subject

Basics for Building Access 2007 Runtime-Based Solutions
Find out how to prepare your application for use with the Microsoft Office Access 2007 Runtime.
Microsoft Access Runtime Distribution Programs and Free Downloads
Microsoft offers runtime versions of Microsoft Access so you can create database applications in MS Access and distribute them to non-Access owners.

 

9 responses on “Microsoft Access Runtime”

  2. Lori Krist

    I need to upgrade our runtime users to either Access 2016 RT or O365 RT. I’m having problems with both.
    1. 2016 RT – wants to run Windows installer every single time a database is opened. I’ve edited the registry, and that doesn’t help.

    2. O365 RT – Installs fine, runs fine, however, we use a .vbs script to open databases to allow multiple users to open the same database. The script opens Access.exe and appends the user’s userID at the end. When using the .vbs script in O365 RT, I get the following error message: Unrecognized database format: S:\Network_Address\Database_Name.vbs

    O365 Cont…The vbs script pointing to C:\ProgramFiles\Microsoft Office\root\Office16\MCACCESS.EXE

    If anyone has any ideas/suggestions on how to get either runtime to work, I would be very appreciative.

  3. Darrylle SUNDERLAND

    I have business-critical databases which ‘drop’ tables and recreate them, and delete physical query objects and recreate them – on the fly. I’m having problems with the company suddenly insisting on MS Access ‘Runtime’ for end-users.
    Can MS Access ‘Runtime’ perform these actions for the end-user (embedded in code of course).

    1. Daniel Pineault Post author

      Darrylle,

      Your best bet would be to launch your database using the command line /runtime switch and test all the functionalities. See the section ‘Simulating Runtime’ from the article above.

      Even better, create a VM that mirrors your client’s environment, install the runtime version of Access and then test things out.

  4. Frank Sellers

    I’ve never used Runtime before but I’ve been charged with helping users decide if they want Access 2013 Runtime or the full version, and Microsoft’s own website is short on details (at least I can’t find anything but download pages like the link you provide above). I don’t have Runtime on my own computer and someone asked if Runtime users can go directly into tables. My answer: “Um… I dunno!” Do you know? You only reference the Linked Table Manager here. Do you know of a website that details the details? Thanks.

    1. Daniel Pineault Post author

      Yes and no.

      Runtime doesn’t display the navigation pane, but you can still open table if you add the necessary code to do so to your Application Ribbon or Menu.

      DoCmd.OpenTable "YourTableName"

      Don’t forget, you can use command-line switches (/runtime) to simulate the runtime environment to get a better idea of how your db will look and behave in runtime. Refer to: https://www.devhut.net/microsoft-access-command-line-switches/

      When developing for runtime, you need to create your own navigation: Ribbon or Menu.

  5. Frank Sellers

    Thanks for the quick response, Monsieur Pineault. (Couldn’t resist!) So if I don’t do any extra coding to allow that, users won’t be able to get directly into tables. And either way (please correct me if I’m wrong), Runtime users won’t be able to change the structure of tables. I’m thinking maybe a sub-form displaying table data would be easier (and safer?).

    1. Daniel Pineault Post author

      You’re always best never to give users direct access to table, and queries. They should be limited to forms and reports where you have more control and can ensure they don’t do catastrophic damage to the database.

      If you give them access to the tables and design, then yes, they can make changes. If you have them all hidden, then they can’t.