Access 2013 apd alternative

[Andrew Barker]

No doubt there are other similar threads. I know that adps have been deprecated from Access 2013. And i have seen the microsoft advice for the various alternatives:
upgrade to 2013, and convert adp to accdb linked to sqlserver tables
upgrade to 2013, and move client to .NET
stay on 2010, and dont upgrade back end past SQL2012
My question is have any of you taken any of these options, and what are your experiences, gotchas etc, as we have to make a decision to go one way or another with our local government in-house databases which are currently access 2002 adp front ends on SQL2008.

 

[Andrew Barker]

Thanks for your advice Pat. To clarify:
For performance and scalability, we are keeping the back end tables in SQL server. Not to mention all the procedures and functions in the back end which we dont want to re-write.
So really its a matter of deciding what to do with the adp client. With the arrival of access 2013, it would be great to hear from those who have already decided what to do with their adp front ends and why.....any pains/success stories?