I have been FLAMED on this group for using DAO.
By an obnoxious twit whose entire contribution to this newsgroup is
flaming other people for giving good advice. Oh, yes, his other
contribution is including at least one nugget of factually incorrect
information in each of his posts.
Pay no attention to Aaron Kempf or any of his multiple alter eagos.
I must admit, I know
nothing at all about it.
You probably know more about it than Aaron does.
The databases I have been working on were
built by somebody else before I started working here. I have just
got the job of maintaining & repairing them. It is not part of my
job to rewrite the whole thing. But for new development, I am keen
to use the latest technology where possible.
Where can I find out about ADP? If DAO is deprecated, what should
I be using?
Here's some information about ADPs, from Microsoft's own
documentation:
From
http://technet2.microsoft.com/Office/en-us/library/1dce641e-ba1c-446a
-8ff2-221769a58ba51033.mspx?mfr=true :
Access Data Projects (ADPs)
An Access Data Project is an OLE document file, like the .xls
or.doc file formats. It contains forms, reports, macros, VBA
modules, and a connection string. All tables and queries are
stored in SQL Server. The ADP architecture was designed to create
client-server applications. Because of this, there is a limit to
the number of records that Access returns in any recordset. This
limit is configurable, but you typically must build enough
filtering into your application so that you do not reach the
limit.
Access uses OLEDB to communicate with SQL Server. To provide the
Jet-like cursor behavior desired for desktop applications, Access
implements the Client Data Manager (CDM) as an additional layer
between Access and OLEDB.
Because of the layers required to get from Access to SQL Server in
the ADP architecture, it is often easier to optimize MDB/ACCDB
file solutions. However, there are some scenarios where a report
might be generated significantly faster in an ADP file. To add
these performance improvements and retain the flexibility of SQL
Server, you can build the majority of the application in an MDB or
ACCDB file and have the file load reports from a referenced ADP
file.
One advantage that ADP files have over files in MDB or ACCDB
format is the ability to make design changes to SQL Server
objects. ADP files include graphical designers for tables, views,
stored procedures, functions, and database diagrams.
So, it's pretty clearly that ADPs are no longer Microsoft's
preferred method for building front ends for SQL Server databases,
for the reasons outlined above.
Just killfile Aaron and all of his alter egos -- you will lose not
one bit of useful information by doing so.
