Best practice: moving from Access 2003 to Access 2010
Posted on 2010-08-31
All our users have been using Office 2003 up to now. We plan to deploy Office 2010 to the uses who will be getting Win 7 PC (we skiopped Vista and Office 2007). Our main concern is that we have a number of databases in Office 2003 that users need to access but not everyone will be getting Office 2010 at the same time, so some users with Office 2003 and some with Office 2010 will be accessing the same databases. That means I cannot just install Office 2010 everywhere and upgrade at the same time.
Most of the users work thru a frontend but some get in the db directly. While setting up GPO deployment of Office 2010 I saw there is an option to force Access 2010 to run in Access 2003 mode.
My question is this:
Are we better off to install Office 2010 without Access and remove all Office 2003 components except for Access 2003
Are we better off to install Access 2010 in the forced 2003 mode instead.
One downside I see right off is that I would have to keep patching an Office 2003 product along with the Office 2010 product if I leave Access 2003 installed.
On one hand when we do get all the users running Access 2003 who access a particular database to Office 2010 we could in theory convert the database at that point to Access 2010 and remove Access 2003 and install Access 2010
On the other hand if I install Access 2010 in forced Access 2003 mode then get all those users to Office 2010 eventually, I could upgrade their database to Access 2010 but then what is the process to change their Access version from the forced Access 2003 to the real Access 2010?