[AccessD] Reporting field properties

We take exactly opposite approaches there, Stuart. First thing I do is look
for the DAO references and immediately start transforming them to ADO +
ADOX. I started out with DAO since there was no alternative, and then I
switched because that was the best way to talk to SQL... and once I got
there I would _never_ go back.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: July 15, 2005 6: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 :-) 

Not to say that I am right, but merely that I am 100 times more comfortable
in ADO + ADOX than in DAO. It just makes more sense to me, plus it works
lots better with ADP + SQL apps.

A.

-- 
Stuart


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