=?Utf-8?B?YnJpYW5r?= wrote in
:

Thank you for your thoughts on this situation. Currently my
employee seems to be firmly in place with using SQL 2005. With
this in mind I am now trying to determine which is best with the
SQL connection, either accdb or adp. I hear opinions supporting
each way but I'm trying to determine what factual evidence is the
most swaying. I appreciate any thoughts on this.

If you have an existing MDB application, no matter how confusingly
architected, you should stick with it and just fix the problems.
Likely when you understand the code you'll realize it didn't get
convoluted by accident. That is, very often convoluted solutions
reflect a previous developer's struggle and resolution of a complex
problem, and the result will encode a lot of factual information
about the problem being solved. Trashing it and starting over with
an ADP will mean you lose all the knowledge reflected in the code
that's been implemented.

That said, yes, sometimes convoluted code comes about because of a
programmer who simply isn't aware of the better methods. But that
kind of code is usually quite easy to spot and therefore pretty easy
to upgrade to better methods.

If you were starting with new development, I'd say 40/60 likelihood
that ADP is the best choice. After all, MS has been deprecating ADPs
for the last several years, even for new development, with the
exception of reporting apps (which MS says do have certain
performance advantages in ADPs).

But all of this will change 2-3 years from now, with the release of
Access 15, which apparently is going to address the neglect of ADPs
in the last two releases. That isn't enough to convince me that it's
wise to trash an MDB app and replace it with an ADP even then, but
it's worth keeping in mind (i.e., the investment in moving to ADP
could pay off 2 or 3 years down the road; on the other hand, the
Access 15 ADPs could be sufficiently different to make current ADPs
problematic).

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/