access 2002 vs 2003

W

Whitney

I made the mistake of designing a report using access 2003 on a database that
is used everyday by Access 2002 users. It works great for me but the 2002
users are getting missing reference errors and fields that were automatically
populated, such as with today's date, are now given ##NAME?## errors.
I've tried to copy files into the DAO folder or the Microsoft Web Components
folders but I'm not getting anywhere...
any help would be great.

Thanks
 
R

Rick Brandt

Whitney said:
I made the mistake of designing a report using access 2003 on a
database that is used everyday by Access 2002 users. It works great
for me but the 2002 users are getting missing reference errors and
fields that were automatically populated, such as with today's date,
are now given ##NAME?## errors.
I've tried to copy files into the DAO folder or the Microsoft Web
Components folders but I'm not getting anywhere...
any help would be great.

Thanks

Since Access 2003 (as well as 2002) still use the 2000 file format by
default it is very likely that the fact that you used A2003 is not relevant.
What you are describing can happen any time you develop on one PC and try to
use the app on another.

First thing I would recommend is that you open a new blank file on your PC
and look at the default references that are present. Then look at the
references on the app in question. Are there additional references? If so,
why? It is seldom a good idea to include additional references in an app
that you want to distribute to multiple users and 99% of the time the same
functiunality can be achieved without adding those references.

It's also possible to end up with additional references when you are just
experimenting with various controls that you ultimately don't use. In these
cases those extra references can just be removed thus eliminating your
problem.

If you have intentional additional references to support functionality in
your app there are often ways to achieve that same functionality without
adding a reference, either with an API call or by using Late Binding. In
addition to eliminating the "bugs" associated with missing references, Late
Binding usually makes your app version independent for the external library
being used. For example if I automate Outlook with a reference then all
users have to have the same version of Outlook installed. With Late Binding
they merely need *any* version of Outlook.

Another plus with Late Binding is if a user were ot not have Outlook
installed at all, then only the portion of my app that tried to automate
Outlook is affected. With a reference added you get all of the these Date()
and other problems.
 
Top