Access 2010 ADP or MDB

Hi All,

Anyone got any official notes/guidance to say wether using an Access SQL Project (ADP) is recommended for Access 2010 when using an SQL backend?

I've got an Access 2007 ADP project and I'm wondering if I should convert to an MDB or continue with ADP.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
ADPs are still supported as of 2010, in the same manner as they were in 2007. If you have a working ADP I see no valid reason to change to linked tables. Note that support for ADPs is limited in newer versions of SQL Server (2005 and 2008). The limitations are in the design areas, which you can get around by using SSMS, but to me that doesn't bode well for ADPs.

See the posts from Mary Chipman of Microsoft here, but please ignore the rantings of Aaron Kempf, who is a scourge on the Access newsgroups:
Vadim RappCommented:
Depends on what you want to do with this ADP. If you expect significant further development, then maybe it will make sense indeed to convert to MDB, or even to Visual Studio. If just use it, then of course, why bother. (But then why would you mention 2010).
jmsjmsAuthor Commented:
THe database isnt static.  We continually modify it and we will be getting Office 2010 at some stage.  Hence my question about wether to carry on with an ADP or move to MDB.

I've just seen so much unsubstantiated stuff on the net about MS ditching ADP...

Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

Vadim RappCommented:
I'm pretty sure the unsubstantiated stuff was actually originating from MS itself, depending on the direction of the political winds there in every particular moment.
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Still, I see no reason to move to move to .mdb if you have a working file. There are significant changes in 2010, but none that would affect an existing ADP or MDB app, or that would affect any changes you may wish to make.

If you are embarking on a NEW project, then the prevailing winds seem to say to use the .mdb/.accdb format with linked tables.

IIRC, according to MS the number of people using the .adp format is very, very small. MS would, of course, like to put their money into the right channel, and will focus their energies on the areas most widely used. In other words, while you probably won't see support for ADPs removed you also won't see much going toward implementation of new ADP related features (like design support for newer versions of SQL, for example, or direct integration with new SQL features, etc etc).


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Vadim RappCommented:
> changes in 2010, but none that would affect an existing ADP or MDB app,

This very area on EE is the evidence that at least in 2007, there were lots of things that affected an existing ADP. And, remarkably, all affected in the same direction. "My adp worked in A03, why this does not work in 07". "Why in 07 this became 100 times slower". "Why filter button became disabled" (the most recent one I remember).

I guess, product with _that_ toolbar* simply can't not to ruin an application.

*) or, more seriously, with _that_ attention paid to the toolbar by the developers
jmsjmsAuthor Commented:
Thanks for your input Experts.  I'm going to carry on with the App in ADP but when time permits move back to MDB or consider using dotNet.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.