469,267 Members | 1,189 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,267 developers. It's quick & easy.

access2000 dao / ado - can references order by changed programatically

I've got an access97 app that is being converted to access2000
a dao recordset is different than an ado recordset, and whether or not
the app works is determined by the priority of the libraries in the
reference list

is there some vba code that can
a) tell me which of the 2 (dao or ado) is first in the list
b) switch the order to put dao first if required
I know that the vba code can be changed to dao.recordset, but there's
lots of those
Nov 13 '05 #1
2 1533
"Roger" <le*********@natpro.com> wrote in message
news:8c**************************@posting.google.c om...
I've got an access97 app that is being converted to access2000
a dao recordset is different than an ado recordset, and whether or not
the app works is determined by the priority of the libraries in the
reference list

is there some vba code that can
a) tell me which of the 2 (dao or ado) is first in the list
b) switch the order to put dao first if required
I know that the vba code can be changed to dao.recordset, but there's
lots of those

So how many seconds would it take to convert "As Recordset" to "As
DAO.Recordset" using Access's built-in find and replace functionality? If
you're just starting the conversion process, there shouldn't be any
ADOB.Recordsets as it was written for Access 97.
Nov 13 '05 #2
le*********@natpro.com (Roger) wrote in message news:<8c**************************@posting.google. com>...
I've got an access97 app that is being converted to access2000
a dao recordset is different than an ado recordset, and whether or not
the app works is determined by the priority of the libraries in the
reference list

is there some vba code that can
a) tell me which of the 2 (dao or ado) is first in the list
b) switch the order to put dao first if required
I know that the vba code can be changed to dao.recordset, but there's
lots of those

Your best bet is to disambiguate your references. If you prepend
"DAO." to all your objects, you should be fine. Then you can use
GetReferenceFromFile to register the DAO library if you want. If you
don't, any object that is also in the ADO object model will cause an
error.
Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

12 posts views Thread by A-PK | last post: by
2 posts views Thread by Mike Metzger | last post: by
3 posts views Thread by Bruce Acciavatti | last post: by
4 posts views Thread by Adam Ratcliffe | last post: by
9 posts views Thread by DrConti | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.