broken references with shared database

[Michel Peeters]

We are sharing a .mdb file on the document server.
Some users are in Access 2002, others in Access 2007.
Problem: reference is made to Microsoft Excel Object Library 10.0 on the
2002-PC.
If the 2007-PC opens the database, Access changes the link automaticly to
Microsot Excel Object Library 12.0
But if after that a 2002-PC opens the database it results in a Broken Link
Error.
How can I solve this?
Tks

 

[Rick Brandt]

We are sharing a .mdb file on the document server.
Some users are in Access 2002, others in Access 2007.
Problem: reference is made to Microsoft Excel Object Library 10.0 on
the 2002-PC.
If the 2007-PC opens the database, Access changes the link
automaticly to Microsot Excel Object Library 12.0
But if after that a 2002-PC opens the database it results in a Broken
Link Error.
How can I solve this?
Tks

Switch to late binding (search these groups). That will make your Excel code
(in almost all cases) version independent.

One should almost never add references beyond the defaults to an Access file
that needs to run on multiple systems unless you can guarantee that all of them
are set up identically.

 

[Douglas J. Steele]

In addition to what Rick suggests (Late Binding), if you're running into the
problem you're encountering, the implications are that your users are all
opening the same MDB file.

The recommended approach is that all multi-user applications be split into a
front-end (containing the queries, forms, reports, macros and modules),
linked to a back-end (containing the tables and relations). Only the
back-end should be on the server: each user should have his/her own copy of
the front-end, preferably on his/her hard drive.