Update to: 2007, 2010 or 2013?

[supmktg]

I've created a number of applications using Access 97, 2000 & 2003, which I distribute as an mde. Generally, they are attached to an sql server database and contain many forms and reports with quite a bit of vba code.

I've resisted upgrading past 2003 because most of my users are still using 2003 or they are able to run the application in 2007 or 2010 with no issues. I am about to replace my laptop, and also begin a new project for someone using 2013, so I think it's time for me to upgrade.

Should jump right to 2013, or go with 2010 or 2007 for some reason?

I appreciate any advice you have!

Thanks,
Sup

 

[Pat Hartman]

Normally, I would say go with A2013 but before you do, you should examine the what's missing articles to make sure that you aren't loosing a feature that you use everywhere. Things like Treeview, PivotTables, PivotCharts, dBase and working with versions of Access earlier than A2000 are gone.

My second choice is A2010 if you can't get past something that has gone missing in A2013. A2007 isn't even a contender.

 

[sjdeetz]

If your mde uses a fair amount of ADO to get into SQL Server you might want to stick with 2010. I could be misinformed but ADO is getting deprecated in Access 2013 and in SQL Server 2014. If you use ODBC with your code you should be fine.

 

[ions]

I have wanted to upgrade for a while now but you can't have Access 2007, Access 2010 and Access 2013 installed on the same machine without using Virtual machines.

If you build your solution in 2013 or 2010 it won't run for your users that are running 2003 etc... you will have to install a runtime for them.

Also based on my understanding Access 2013 does not give you any new features for desktop development but deprecates many features as was stated above.

 

[supmktg]

Thank you Pat, sjdeetz & ions for your very helpful advice! It seems to me that A2010 is the way to go.

Thanks,
Sup

 

[gemma-the-husky]

I have wanted to upgrade for a while now but you can't have Access 2007, Access 2010 and Access 2013 installed on the same machine without using Virtual machines.

If you build your solution in 2013 or 2010 it won't run for your users that are running 2003 etc... you will have to install a runtime for them.

Also based on my understanding Access 2013 does not give you any new features for desktop development but deprecates many features as was stated above.

i have A2003, a2007 AND a2010 peacefully co-existing