Our IT department has decided that the whole company is to upgrade from Access 2013 to 2016.
Unfortunately, this will be done over a 7 - 10 day period, meaning that some people will be running 16 while others are still running 13.
Everyone has their own front end file, so the fact that the references will change for some before others isn't as much of a problem as it would be if they shared a front end. Where I'm curious (nervous?) is what effect, if any, it will have on the shared back end file?
Hypothetical situation: User A is running his own front end under Access 2013, User B is running his own front end under Access 2016
1. If user A accesses the back end and user B accesses it at the same time, will this have any bad effects?
2. If user B opens and closes the back end directly, will this change user A's ability to later open it using their front end?
We've had a few occasions where the back end file has gotten into an 'inconsistent state' and I'm worried it may have been caused in some way by the two version thing.
Unfortunately, this will be done over a 7 - 10 day period, meaning that some people will be running 16 while others are still running 13.
Everyone has their own front end file, so the fact that the references will change for some before others isn't as much of a problem as it would be if they shared a front end. Where I'm curious (nervous?) is what effect, if any, it will have on the shared back end file?
Hypothetical situation: User A is running his own front end under Access 2013, User B is running his own front end under Access 2016
1. If user A accesses the back end and user B accesses it at the same time, will this have any bad effects?
2. If user B opens and closes the back end directly, will this change user A's ability to later open it using their front end?
We've had a few occasions where the back end file has gotten into an 'inconsistent state' and I'm worried it may have been caused in some way by the two version thing.