Hi, Jerry.
It seems that the order of the list is important.
If precedence or speed are required, then the order of these references is
extremely important. Otherwise, just having the correct libraries
referenced is adequate. Disambiguating objects and their methods and
properties will override the need to set library precedence when objects of
the same name are included in more than one library.
My question is, what is the recommended correct order and
is my list complete???
It depends upon the database application. Does the code use ADO? If yes,
then your list isn't complete. If the code doesn't use the OLE Automation
library, then this libary shouldn't be included in the list.
Without seeing your particular database application, we can't give more than
generic advice. An easy way to tell if the necessary libraries are
referenced is to compile the code. If it compiles successfully, then the
libraries are sufficient (but that doesn't preclude other errors, such as
logic errors). But to prevent future problems with missing references, only
include the minimumally necessary references for the code to run. Get rid
of any libraries not used in the VBA code.
My applications do not use any Active X components.
An excellent way to avoid versioning problems and database application
deployment problems.
I build my applications with Access 2000 and then convert
them to Access 97 so I can distribute both.
Developers usually have fewer problems by developing in the oldest version,
then converting to the newer versions, testing all versions, then deploying
the application. Besides, Access 97 is more stable than Access 2000, even
with the service packs installed.
I could not find any help in the Microsoft knowledge base.
The KB is a good place to start. The next place to check is Google Groups
for archived newsgroup messages to determine whether anyone else has had the
same problem as you have and, if so, what others suggested to solve it. The
beta version (i.e., buggy version) is on the following Web page:
http://groups-beta.google.com/group/microsoft.public.access?hl=en&lr=&ie=UTF-8
The old style version, but with the most recent posts from three to nine
hours ago, is currently available on the following Web page, but it's going
to be converted to the beta version soon, too, even though the bugs won't be
fixed for quite a while (if froogle.com beta is any indication, this could
be years from now):
http://groups.google.es/groups?hl=en&lr=&group=microsoft.public.access
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
Beware to those who use munged addresses: known newsgroup E-mail harvesters
for spammers are (e-mail address removed) and (e-mail address removed)
