CPGDeveloper
Board Regular
- Joined
- Oct 8, 2008
- Messages
- 190
Hello~
I administer an MS Access Based DB Application with an Azure SQL Back End. Approximately 25+ End Users.
Each User has a copy of the .accde on their desktop, and I have batch scripts written to copy newer versions of the front end onto their desktop when there is an update.
All of us currently have 32-bit versions of MS Access, with a 64-bit version of Windows 10. However, in the next few months, we will be adding 20+ more users, and many of them will have 64-bit versions of MS Access. And slowly, everyone else will be upgraded, but for quite some time I will have some 32-bit Access Users and some 64-bit Access Users.
I don't see any clever way around this -- I think I would have to manually provide versions to the 64-bit folks, and always have two versions ready for every update. Anyone else experienced something like this?
I administer an MS Access Based DB Application with an Azure SQL Back End. Approximately 25+ End Users.
Each User has a copy of the .accde on their desktop, and I have batch scripts written to copy newer versions of the front end onto their desktop when there is an update.
All of us currently have 32-bit versions of MS Access, with a 64-bit version of Windows 10. However, in the next few months, we will be adding 20+ more users, and many of them will have 64-bit versions of MS Access. And slowly, everyone else will be upgraded, but for quite some time I will have some 32-bit Access Users and some 64-bit Access Users.
I don't see any clever way around this -- I think I would have to manually provide versions to the 64-bit folks, and always have two versions ready for every update. Anyone else experienced something like this?