Re: Access front end for sql server

"lyle fairfield" <lyle.fairfield@xxxxxxxxx> wrote

I think this is not correct, For instance, Access 2003
ADPs allow setting an ADO recordset as a report's
recordset. Access 2002 ADPs, (nor any MDBs,
TTBOMK) does not have this capability.

As far as I have been able to determine, there were no "enhancements" to ADP
in Access 2007, though there were some "make it work" changes.

The general notion among MDB aficionados that
ADPs are separate but equal is prompted, IMO, by
the those aficionados' lack of ADP experience.
ADPs are superior creatures in many ways.

I would have to defer to Lyle's obviously-more-extensive experience with
ADP, but my meager experience with ADP only indicated that using it was not
as onerous as some have thought, but I could see no compelling advantage in
the (relatively straightforward) processing that was done in that
application.

ADO may, as Lyle has stated, have a "simpler object model", but all the same
information is required... it's just that some of it is being provided in a
different way. I'm sure it it good to have "choice" in how you do things,
but the fact that ADO has several ways to accomplish most operations will
mean a learning curve for even accomplished programmers whose previous
experience with Access has only included DAO.

My view may be affected by the fact that the design and implementation of
the ADP application I was engaged to modify was atrocious, but with the same
author, I admit that it would likely have been equally atrocious if it had
been an MDB using DAO. From the programming style, I would guess the person
was a "refugee from VB", not at all familiar with database.

The client, however, was adamant that there be no changes other than the
functional enhancements they had identified, because the function was to be
included in the enterprise requirement planning ERP system they were
implementing, in "just a matter of a few months" and they just wanted to
nurse the Access / SQL Server app along until it the ERP system was ready.

I was not hired to advise on the ERP project, so I didn't. However, the
follow-up is: I know my colleague on that project was still doing minor
changes to the Access application over two years later, so I have to guess
the "few months" stretched a little. That's a lot better than many ERP
projects, which soak up resources for years before being cancelled and
abandoned.

Larry



.

Relevant Pages

  • Re: What is the best way to work with SQL SERVER data / tables?
    ... So by this do you mean manipulating the views from within Access ADP ... ADO and DAO. ... I read somewhere where ADO may not be as flexible as DAO. ... the potential it will have with SQL Server while ...
    (comp.databases.ms-access)
  • Re: Converting Application from ADP to ACCDB
    ... to a stored procedure that I know of is with ADP. ... I hadn't considered using a disconnected ADO recordset and trying to bind ... with using an ACCDB database file instead of an ADP project. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: ADO VS. DAO
    ... DAO is superior to ADO when using Jet data. ... It's not a matter of whether it's an ADP or an MDB, ...
    (comp.databases.ms-access)
  • Re: adp vs mdb
    ... and those layers are no better at the job than Jet. ... situations in which an ADP would be preferable, ... ADO has a lot of advantages when it comes to ... I'm not particularly recommending ADP or MDB or ACCDB; ...
    (microsoft.public.access.adp.sqlserver)
  • Re: ADO VS. DAO
    ... Base, newsgroups, etc. with recommendations for ADP and ADO, the ... ODBC, and server DB over ADP, ADODB, and server. ... ADO exclusively via recordset connection properties with no linked ...
    (comp.databases.ms-access)