[AccessD] Question on Reference (DAO)

It's really up to you.  In many cases, DAO is faster and when you're
dealing with Access UI objects, like forms, controls, etc., you pretty
much have to use DAO.  Later versions of ADO (and Access) handle ADO
better and make it a very practical method for handling data.

Just make sure that if you mix them or even if you don't, you get into
the habit of specifying the object model in your declarations, like Dim
rst As DAO.Recordset.  That will keep you out of trouble down the road.

Charlotte Foust


-----Original Message-----
From: John Clark [mailto:John.Clark at niagaracounty.com] 
Sent: Wednesday, February 09, 2005 10:51 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] Question on Reference (DAO)


I am working on a new program in A2K. Most of my older existing stuff is
A97, and I just used some old code which had a problem. Basically, I
took some code I was using, from an A97 db, to add items to a combo on
NotInList...I think the code was originally written by Dev Ashish. I got
a "reference" error, so I went into the references and added Microsoft
DAO 3.6 object library, and it is working now.

My question is this; is this alright, or should I have adapted the code
to fit 2K? Is there any penalty that I risk (i.e. speed, etc.) by
keeping it this way?

Thanks, 

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