[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 345
  • Last Modified:

Database Deployment - conversion from Access 2003 to 2010

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???
  • 2
1 Solution
MrSlithyAuthor Commented:
In the past, I had local FEs copied down to each desktop. I am thinking about just sticking with network FEs also
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
"In the past, I had local FEs copied down to each desktop."
MUST do.

"I am thinking about just sticking with network FEs also"
Must NOT do.

Each user should have a copy of the FE on their local workstation, linked to the common BE. This is the tried and tested approach used by most all Access pro developers.

There should be no issue of an A2003 BE linked to an A2010 FE ...

"If I have access 2003 and 2010 both installed "
I suggest not ... modifying an A2003 MDB in the A2010 environment, an then opening the MDB back in the A2003 environment ... if that is what you are asking.  Many people have had corruption issues in doing so.

On the flip side, there s/b minimal or no issues working with an MDB in the A2010 environment.

MrSlithyAuthor Commented:
Thanks MX,

As soon as I wrote that about network based FEs, I knew I was wrong. I was just hoping all the corruption issues I recall during my research in 97 to 2003 might be no more. I will heed your advice.

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now