Should I use my ADO experience when using VBA with MS Access 2000

[Guest]

Dear List,

I have to make an input tool using MS Access 2000. I have already alot of
experience using ADO, but outside of MS Access and VBA.

I am really learning now how to use the MS access forms environment, and
wondering if I should use the code generated by the ACCESS wizzards (which is
none ADO - the recordset code is hidden) or use ADO and assign ADO recordsets
to form objects, and do everything manually.

What do you guys think would be easier for me, and better practice ?

regards
Ben Bookey
MCP Visual Basic 6.0

 

[Khai]

Why make it harder writing add'l code for something that Access could do
inherently? (did I use that word correctly?).

I'm all for knowing how to do something multiple ways, but - reinventing the
wheel is not always the best course of action. I'd just look at the end
result, and what's easier way to get there. Why use Access at all, if
you're going to rewrite how to update records when it already knows how?

-Dpharr

 

[Graham R Seach]

Ben,

ADO is intended for accessing data in external data sources, whereas DAO was
written specifically for accessing data in Jet databases. DAO is optimised
for Jet, and quite frankly outperforms ADO when used against Jet.

So, if your data store is Jet, then use DAO. If it's not, use ADO - except
if you're using linked tables, in which case you're using Jet anyway.

Regards,
Graham R Seach
Microsoft Access MVP
Sydney, Australia