Reference Libraries Interchangeability-Acc2000 & Acc2002

[Jim Ory]

Using WinXP & Access 2002

After designing a simple database in Access2002 I shared it with another
back-up user. He is running Access2000. I confirmed that some of the
reference libraries are different in a few cases, which I had assumed would
happen.

The question is then; can Access2000 use the Access2002 libraries if the
Access2002 libraries were copied to his computer, then those new libraries
accessed via the Access database program?

 

[Allen Browne]

Yes, this is a common problem.

The first and most crucial design principle is to avoid any references that
are not absolutely essential. This is especially important because one bad
reference breaks not only the code that depends on it, but the entire
application.

Ideally, pare it down to just 3: the compulsory VBA and Access libraries,
and DAO. Though these change between versions, Access handles them
correctly, i.e. they will not break your application.

If you do need to refer to the libraries of other Office products (such as
Outlook or Excel), use late binding. More info and example:
http://support.microsoft.com/kb/201710/en-us

For other things like calendars, use an Access form instead of an ActiveX
control. Example:
http://allenbrowne.com/ser-51.html

Similarly, avoid things like the FileDialog object, and use the API call
instead:
http://www.mvps.org/access/api/api0001.htm

For suggestions on how to check if the libraries are valid:
http://www.trigeminal.com/usenet/usenet026.asp?1033

 

[TC]

Jim, IMHO you are not really trying to solve the problem: "How can I
use Access 2002's libraries with Access 2000?". You are trying to solve
some other (unstated) problem. What is that other (unstated) problem?

TC (MVP Access)
http://tc2.atspace.com

 

[Jim Ory]

TC, Because you asked and the (unstated) problem was not obvious to you; I'm
ignorant.

Former threads on this subject were very light and I am still a beginner,
well maybe just above a beginner. That's why I post questions here, to help
me overcome my ignorance. If I am designing a database poorly, then I would
like to learn how to design it better. Because of my ignorance, I may have
asked the question incorrectly.

If you are referring to my reference to a "back-up" user as your basis for
the (unstated) problem comment, that is easy to explain. The database I
programmed is a roster of people, trained in emergency communications
techniques, their contact information, equipment information, etc. During our
'hurricane' season, we have to evacuate our island (occasionally) and it is
important to have more than one person able to access the database from
different locations for the personal contact information, etc. needed for
implementing disaster recovery operations.

I did not feel it necessary to explain why I needed to ask the question
because of the room it would take up and it did not add anything to explain
the question.

I've learned so much in this discussion group and am thankful for all the
knowledge other users have provided, including answers you have posted in
other threads.

HTH

 

[Jim Ory]

Allen,

Thank you for the sources. It is easy to get confused designing databases to
do certain things with all the different ways to do them, only to find that
mixing processes produces more problems.

The more I learn, the more I realize how little I know.

 

[TC]

Hi Jim

Friggin' Google Groups has just deleted my whole *&^%$# reply to your
original &^%##@ post so I am rather &%^$#@@! and *&^^%%$$# and **&%$ at
this point !!

I'm sorry if my previous answer was curt, I did not mean it to be. My
point was, you have described your proposed solution - ie. to copy the
A2k libraries to A2k -but you have not described the actual problem.
Perhaps your database uses a function that works for you, but does not
work when you copy the database to the other people? We actually don't
know what the problem is - because you haven't told us (unless I have
missed that, which is possible!).

So I'm just suggesting that you describe the actual problem, instead of
your proposed solution.

Thanks for your comment about previous answers that you got from me. My
sole aim, in posting to these newsgroups, is to help people improve
their usage of Microsoft Access. Hopefuly this succeeeds, more often
than it fails!

HTH,
TC (MVP Access)
htp://tc2.atspace.com

 

[Jim Ory]

TC,

I understand your frustration of your original post being deleted.

The first time I attempted to share my database, multiple items did not
function correctly or not at all-possibly half dozen. I came back to
discussion groups and found that different libraries are used for different
version applications. My second attempt to share resulted in different
failures. Now I have about a dozen things that went wrong. I checked the
references, found missing references and different version references.

When I troubleshoot anything, I look for the simplest solution first, then,
work up to the more complicated. No sense in re-building an engine when all
you need is a gallon of gas. In database terms, re-write the IIF statement,
don't re-design the whole database.

So, my original question was; here is a problem (references, which was very
obvious) and is the simple answer, just share the references between the
versions? Or is it more complicated than that? (Although it wasn't stated
exactly like that.)

I'm sure I'll be back looking for more answers and I hope you'll again take
the time to help me out.