Database Deployment - conversion from Access 2003 to 2010
Posted on 2014-08-13
OK. I am planning on upgrading network databases from Access 2003 to Access 2010. I will start with the FEs, and as I upgrade machines from Access 2003 to 2010, I will switch them over to the new aacdb front ends.
I will still leave all the back ends as Access 2003 until I get 03 Off of all computers (except mine of course, for future BE upgrade).
In the past, when I was involved in a conversion from Access 97 to Access 2003, I was really worried about messing up the old JET database an having databases upgraded by users. I had a registry fix to have Access 2003 NOT ask the upgrade question.
So far, the testing from 2003 to 2010 is going much easier. I am converting copies of the FEs and having them work with copies of the BEs - as I work out any problems.
Are there any real gotchas here? If I have access 2003 and 2010 both installed and I am bouncing back and forth between production and test . . . . do I run the risk of touching a 2003BE with Access 2010 and somehow "poisoning it" so I cant open it in 2003 ant longer? If I follow my proposed method of deploying 2010 aacdb FEs side by side with the old 2003 FEs and leaving all the 2003BEs alone until after the FE upgrade and Office upgrade on computers, will I BE OK? Can aacdb FE and a 2003 FE access the same 2003 MDB BE(s) without any problem???