[AccessD] Reporting field properties

Hi Stuart:

I must say that agree with Arthur on this approach. The ADO connection layer
allows so much flexibility when writing Access applications. Most of my
clients initially started out with small applications but as they grew they
always moved to a MS SQL or Oracle backend. If I had written the program in
DAO it would have been a huge and expensive re-write.

Jim 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
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