I was hoping to find something more specifically about DAO though, just as
I
am able to buy books on T-SQL. I was hoping for something just covering
the
DAO object model and syntax.
Hum, well, I suppose some documents on converting DAO to ADO would help!!
There is a good one in the knowledge base...but it is down as I write
this...
Here is a good one:
Am I correct in the information I have received before that it is better
to
work with DAO than ADO in dealing with Access?
It *can* be a bit better, but is rarely a deal breaker here.
What is your opinion of ADO vs. DAO with Access DBs I have agood handle on
ADO from writing .asp and .vbs for about 6 years?
Oh, gee, you eat and think in ADO. Go with it!!. You might as well leverage
your skills here. The DAO object model simply came before ADO. Ms-access
happily supports both. I would stick with ado. The differences are little,
and I can't see even issues of performance making a difference here.
'An example DAO vs ADO recordset loop, you'll see how similar they are:
'--- begin DAO ---
Dim rst As dao.Recordset
Set rst = CurrentDb.OpenRecordset("select * from contacts")
Do While rst.EOF = False
Debug.Print rst!FirstName
rst.MoveNext
Loop
rst.Close
Set rst = Nothing
'--- end DAO ---
'--- begin ADO ---
Dim rs As New ADODB.Recordset
rs.Open ("select * from contacts"), CurrentProject.Connection
Do While rs.EOF = False
Debug.Print rs!FirstName
rs.MoveNext
Loop
rs.Close
Set rs = Nothing
You got the currentProject.Connection that gives you ready a connection
object at all times. So, I would use ADO. It is newer, and it is what you
know. About the only disavantage here is that a "ton" of example code etc.
is posted in DAO...
