Access runtime database not working with Access 2016

Question

I have an application that has an Access Runtime database as a front end.

This database is opened via a shortcut that uses commandline parameters.

It works fine on nearly all configurations of Access and Windows from Access 2010 and Windows 7 onwards, including on Windows 10 running Office 365 with the full version of Access installed.

However on one or two systems running Windows 10 with the full version of Access 2016 installed, when the shortcut is executed the database is opened but is then immediately closed, which is the behaviour that I would expect if the command line parameters were invalid.

I can get round the issue by downloading and installing Access Runtime 2013 alongside the full version Access 2016.

The runtime database then behaves normally.

This implies that there is something within Access 2016, possibly a setting, that is preventing it from recognising the parameters that are being passed, but I cannot find anything.

Can anybody help?

Answer 1

Access Runtime is the same as the full version of Access with the design features removed. In fact, if you already had the full version installed, then I don't believe you can install the runtime. The installer may run, but I'm fairly confident it will exit if it detects the full version. If that didn't happen, then you could have had an issue with the install of the full version on the machine.