Hi, guys here:

Thank you so much for all your kind replies. You are so helpful.

After testing, I still have the question to JpJoe.
If I priorities DAO above ADO, does it mean I'm using DAO. Since I need a multi-user environment, actually I have split my database and have a backend and several frontends, do you think ADO is suitable for me? In that case, I'm wondering if there is potential problems with DAO + ADO in the future?

Right now, I prefer to use ADO + DAO (priority my ADO above DAO), since explicitly declare works well. But I don't know if there is other problems or trouble down the road.

For Loralee, you are right, I'm learning through the sample in that book:)

Both the sample code and the code provided by Dartcoach work well with only DAO reference, and also work well after explictly declare with ADO + DAO.

But as you say, I always want to learn. If convenient, please email yours to me. Thanks a lot!

Again, I really appreciate all the help and your time.

NeoCat

DAO can be a problem if you want to move your application anywhere. You will need to visit all your users machines and set the DAO reference. That can be a pain. I have moved off of DAO to prevent this from being an issue. My users are blocks away sometimes.

mmcdonal

JP
Thank you!

One more question.....

By using the recordsetclone of the recordset, am I really gaining anything over using the recordset directly ?

(Couldn't the same thing be accomplished either way?)

Thanks,
Loralee