Upgrading access 2003 to 2010 or 2013
Posted on 2015-01-22
We are moving a client app from Access 2003. Our staff has worked with 2010 but not 2013, so the initial plan was to move to 2010 since we are familiar with it. The client is asking why we aren''t going to 2013?
When we began upgrading 2003 apps a while ago, I posted a question EE as to whether to upgrade to 2010 or 2013, which were both available. This was over a year ago. At that time I remember the responses suggested that it was a more direct path to upgrade from to 2003 to 2010, than to upgrade from 2003 to 2013. But I don't remember why.
So I'm asking the question again. We're upgrading a 2003 app, hoping to keep as much functionality as possible without re-coding. The app has thousands of lines of VB code. Is this supported in 2013?
Is there any reason to upgrade to 2010 instead of 2013?