Greetings to the well of knowledge...
We recently upgraded on Office 2016 including Access 2016 runtime at our HQ. We have several remote locations still running Office 2010 with Access 2010 runtime. We have plans of upgrading these remote locations but we have some logistical issues :banghead:to overcome first.
Because of this, I am still doing development in Access 2010. I have had reports from some of my HQ users that our primary DB crashes with the high-informative "Execution of this application..." error. I have been unable to reproduce the error in my development environment.
So, in order to diagnose these problems, I installed full-version Access 2010 on their PCs. Low and behold, the DB now will not crash.
Which leads me to think: are there issues running an Access 2010 database using Access 2016 runtime? Is this something that anyone can shed some light on?
Kind regards,
Ken
We recently upgraded on Office 2016 including Access 2016 runtime at our HQ. We have several remote locations still running Office 2010 with Access 2010 runtime. We have plans of upgrading these remote locations but we have some logistical issues :banghead:to overcome first.
Because of this, I am still doing development in Access 2010. I have had reports from some of my HQ users that our primary DB crashes with the high-informative "Execution of this application..." error. I have been unable to reproduce the error in my development environment.
So, in order to diagnose these problems, I installed full-version Access 2010 on their PCs. Low and behold, the DB now will not crash.
Which leads me to think: are there issues running an Access 2010 database using Access 2016 runtime? Is this something that anyone can shed some light on?
Kind regards,
Ken
