Microsoft DA0 3.x Object Library - sql, vba

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

Guest

Im sitting at home creating a Database using MS ACCESS 2000.

i would like to use some of the dao commands in vba to create & run SQL
statements. So, i was told that i would have to go into Tools>References and
click on.....

Microsoft DA0 3.x Object Library

... but does that mean, everyone who wishes to use my database on their
computer has to go into Tools>References and click on Microsoft DA0 3.x
Object Library??

Cheers,
WebDude.
 
No! References are carried through with your database. When a user runs your
database, if he does not have DAO 3.x set as a reference, Access will
automatically set it for him. The only problem you could incur with
references is if you used some obscure library in your database and the user
did not have that library on his computer.
 
The only problem you could incur with references is
if you used some obscure library in your database and did not have that
library on his computer.
Click to expand...

Or ... used some COMMON library ... and ...
Or ... that library in the SAME LOCATION on his computer
Or ... that VERSION OF THE library on his computer
OR ... that library CORRECTLY INSTALLED on his computer

(david)
 
Thanks PC Datasheet for answering my question! :-)



PC Datasheet said:
No! References are carried through with your database. When a user runs your
database, if he does not have DAO 3.x set as a reference, Access will
automatically set it for him.
Click to expand...


...Your answer just begs another question, why isn't the DAO 3.x and, for
that matter, all the other libraries that came with my installation of Access
set to ON ("checked") in the tools>references? Why do i have to set it to ON?
Is it to save memory for the casual user who wont probably need/use those
libraries?


The only problem you could incur with
references is if you used some obscure library in your database and the user
did not have that library on his computer.
Click to expand...

I suppose the list of libraries in the tools>references are just the ones
which came with my installation of MS ACCESS..since i dont recall downloading
ms access libraries..?? However, i was told that the list in tools>libraries
may include libraries that were installed from other programs on my PC? So
then, how do i know if the library im turning on/using in the
tools>referneces came with ms access and is therefore readily accessible to
other pc users who wish to use my database?


:-D

Regards,
WeeeeeebDude!
 
Hi Dave, thanks for replying to my question :-)

Or ... used some COMMON library ... and ...
Or ... that library in the SAME LOCATION on his computer
Or ... that VERSION OF THE library on his computer
OR ... that library CORRECTLY INSTALLED on his computer
Click to expand...

...but i dont follow what you mean. If i use a common library, then im sure
not to run into any problems running my database on another pc, right?
"Same location" ? ANd if he doesnt have the same version of the library, then
it wont work, right?

:-D
WebDude Away!
 
Word is a common library, but you will run into problems
if you reference it on a PC where Word is not installed.

Of the 20 workstations I personally support, 1 does not
have Word installed, plus I have 5 servers that do not
have Word installed.

Even Common libraries are not installed on all PC's.

Nobody here understands the problem with library location.
It ought to work: it seems to work most of the time?????
But sometimes it just doesn't work if the libraries are
not installed to the same location.

So for any widely distributed application, you should use
late binding, ADO or DAO, and then only the built-in
references.

(david)
 
david epsom dot com dot au said:
Word is a common library, but you will run into problems
if you reference it on a PC where Word is not installed.

Of the 20 workstations I personally support, 1 does not
have Word installed, plus I have 5 servers that do not
have Word installed.

Even Common libraries are not installed on all PC's.

Nobody here understands the problem with library location.
It ought to work: it seems to work most of the time?????
But sometimes it just doesn't work if the libraries are
not installed to the same location.

So for any widely distributed application, you should use
late binding, ADO or DAO, and then only the built-in
references.
Click to expand...

Ah. Binding. Sounds like a way to ... incorporate the .. libraries into your
databsae for distribution to other PCs that might not have the libraries
installed... ill do some more research on what exactly binding is.. but You
mentioned "built-in references", sounds like what i was hoping to do - build
a database using only the functions that come with the typical install of
msaccess... i guess i mixed up my words in earlier posts by saying i wanted
to use just the "common libraries" .. when i should have said, just the
built-in libraries that come with the typical install of ms-access.

Cheers mate,
WebDude Out!
 
Back
Top