Deployment and Access Runtime

[Tuckejam]

Have My db split with my backend in SQL Server.



now trying to distribute the front end to users using access runtime.

on the second machine which did not have access I have downloaded and run the Access 365 Runtime application

this appears to have installed some version of Access 16

Having built my Access db in 2019 it wont open the file because it is a newer version of the file.

I have saved the database version to be opend by runtime as accDE.

I did notice however that I can save my Access database for use with Access 2000 - 2003 and am a little concerned and confused that I can save my database to be compatible with something from 20 years ago but not 2016

any thoughts or help is always appreciated

[ranman256]

creating in 2019 doesn’t really get you any advantage.
convert the db to the older version then it will run in all versions foreword.

[Micron]

If you don't mind a bit of guessing, did you create trusted location and put the file there on the pc where you installed runtime version? I cannot imagine it's a compatibility issue between 2019 and 2016. Only other thing that comes to mind is if you developed in 32 bit and the runtime pc is 64 bit, but the message would not be about older vs newer versions; it would be specifically about bitness.

[CJ_London]

Saving as a 2003 version relates more to the tables. If you are saving forms/reports etc then you will probably find that it won’t save because you are using features that did not exist back then. It will only convert if these features have not been used.

The same will go for 2016 - if your FE development includes features not available in 2016 then 2016 runtime won’t be able to run it.

Go to the FMS website for a list of new and deprecated features for each version

Only feature that comes to mind is data types, think there is a bigint type available in 2019 and not in 2016

Another possibility is you are using early binding in your code. If you have specified in vba to use the 2019 excel library example, that version of excel needs to be on the users machine. Using late binding means access will use whatever version is available- again subject to your code not using excel features not available in 2016

Probably too late, but when developing for multi age applications, always develop in the oldest version

Have you tried installing a later runtime? And have you tried running updates on the runtime?