Do I have to Add DAO 3.6 Object Library for every user?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have added code that performs NotInList procedures to my Access 2000 app that uses DAO functionality. My Question is: Do I have to instruct every user to add the Microsoft DAO 3.X Object Library from the VB References?

I think I could do the code in ADO (recordsets for example) except my code uses DAO.Database which does not seem to have and ADO equivalent. Any advice

Thanks
rjkulesa
 
In short, yes you would (unless you use Late Binding).

Better question: What are you doing in DAO? ADO has no Database object
because it's a different object model ... however you can usually do the
same things in ADO (or ADOX) that you can in DAO.

--
Scott McDaniel
CS Computer Software
Visual Basic - Access - Sql Server - ASP
rjkulesa said:
I have added code that performs NotInList procedures to my Access 2000 app
Click to expand...
that uses DAO functionality. My Question is: Do I have to instruct every
user to add the Microsoft DAO 3.X Object Library from the VB References?
I think I could do the code in ADO (recordsets for example) except my code
Click to expand...
uses DAO.Database which does not seem to have and ADO equivalent. Any
advice?
 
rjkulesa said:
I have added code that performs NotInList procedures to my Access 2000
Click to expand...
app that uses DAO functionality. My Question is: Do I have to instruct
every user to add the Microsoft DAO 3.X Object Library from the VB
References?
I think I could do the code in ADO (recordsets for example) except my
Click to expand...
code uses DAO.Database which does not seem to have and ADO equivalent. Any
advice?

The reference to DAO is stored in the file. If you give the file to others
the reference will already be set. Of course the library being referenced
has to exist on the other user's PC, but that shouldn't be an issue with
DAO. While Access 2000-2002 don't use DAO by default, they all install it.
 
Scott McDaniel said:
In short, yes you would (unless you use Late Binding).
Click to expand...


Actaully, the references you set in your mdb file remain with the database.

Since the access install by default has the dao library installed, if you
distribute your database with the dao ref set, then it will be set for all
computers. I have NEVER seen a broken ref due to distribution of a mdb, or
mde file with the dao 3.6 ref set. When you install ms-access, the dao
library is installed, and you CAN NOT avoid this!

For sure, setting refs to libraries that will not exist, or change on the
target computer means that one should use late binding, but the dao 3.6
would not fall in this category at all.

No one would possibility consider using late binding for DAO recordset code
in access application (I don't think you are suggesing this, but it not
clear!). Launching word, or other automation objects is a very large and
processing/memory intensive operation, and thus the time involved to
run-time link (late bind) is insignificant.

However, for recordset code, the time involved for late binding would
represent a huge amount of time, and in fact be a serious performance issue
in most cases. Late binding for general DAO code is simply not a reasonable
solution in a access application. And, as mentioned, if the dao ref is set,
it remains with the mdb file.


--

Albert D. Kallal (MVP)
Edmonton, Alberta Canada
(e-mail address removed)
http://www.attcanada.net/~kallal.msn
 
Hi Albert,

Thanks for clarifying my post. As you mentioned, I would never advocate late
binding for DAO ...
 
Back
Top