[AccessD] Reporting field properties

I can't agree with you, Stuart.  I've created split Access databases
with no linked tables using ADO.  DAO would have been useless for that.
DAO is primarily useful in dealing with the Jet engine structures and
peculiarities and is optimized for that purpose.  It tends to fall on
its face when dealing with anything else.  ADO is intended to handle
data access, regardless of datasource, and I prefer it because it is far
more powerful and flexible than DAO in data handling.  It all depends on
what you do with either one of them.

Charlotte Foust


-----Original Message-----
From: Stuart McLachlan [mailto:stuart at lexacorp.com.pg] 
Sent: Friday, July 15, 2005 3:57 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Reporting field properties


On 15 Jul 2005 at 10:38, John W. Colby wrote:

> That's what I thought.  In cases like this it is useful to be able to 
> get at the physical layer.  DAO is occasionally still useful.
> 

Ocassionally?  

If you are working with Jet(using Access as your data store) I don't
know a 
single advantage of ADO over DAO.  I do know several advantages  DAO has

over ADO.

I use ADO in VB regularly, but every time I create a new Access 
application, the first thing I do is remove the ADO reference and
replace 
it with a reference to DAO :-) 

-- 
Stuart


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com