ADO or DAO, which way to go?

[OneSource]

Hey that rhymed!

On to my question. I'm developing an app that uses an Acess DB that will eventually be stored on a server. There will be more than 1 PC running the app. Given this scenario, what's the best method to connect to the DB, ADO or DAO? I'm concerned about 2 users trying to modify the same data simultaneously (record locking and such).

Thanks for any recommendations.

[RIVES]

I do hope that your app is just small. How many records a day would be encoded? How frequent do you archive data? How many records are you planning to store in the access database...(its only good up to 10,000 records you know.) Have you ever considered Sql server server/desktop?

Anyways, ADO is better...since it the latest among the three (ADO, DAO, RDO). I think that it is just a mixture of both DAO and RDO...it automatically detects DAO or RDO depending on what ODBC driver/ole database driver.

[OneSource]

The App will be relatively small, although I'm not sure how many records will be added daily. For what I'm creating, Access should be able to handle it (I forgot where I saw it documented, but I'm pretty sure that an Access table can have more than 10,000 records).

Anyone else have any opinions?

Thanks again.

[DrewDog_21]

ADO is more versatile. It has plenty of bugs and quirks but
nothing is perfect I guess. DAO is being phased out so
future versions of VB will not include it, and future
versions of Access probably will not support it either.

[OneSource]

Thanks for your feedback although the "bugs and quirks" part has me a little concerned! But I'll go, with ADO. That rhymed too didn't it!

Thanks again.