Library References

[Guest]

Can anybody please confirm to me that Access 2003 cannot automatically
replace a reference to an older version of a library (say MSACC8.OLB) with
the newer version MSACC.OLB. I think that if the reference has been changed
(other than with vba code) then it must have been done manually? Is that
right?
Many thanks.

 

[Norman Yuan]

Your question is not that clear to understand. The reference to MSACC8.olb
or MSACC.olb in what program? As far as I know, different versions of Access
can coexist in the same box, so, different MSACC*.olb could be found in the
same computer, natually in different installation folder, if the user chose
to install different version of Access, instead of upgrading Access to newer
version.

 

[Guest]

Norman,

Sorry I didn't make it clear. I have an application written specifically
for '97 but recently 2003 users have been trying to access it. The
application gives a compiler error when 2003 users access it as they don't
have multiple versions installed. The reference is being linked to the 2003
library, thus causing problems to the intended users. It has been suggested
that 2003 substitutes its version of the library automatically but I don't
believe that is the case. I think it has to be done manually by the 2003
user(s) but I wanted to be sure of the facts.

 

[Douglas J. Steele]

First of all, is your application split into a front-end (containing the
queries, forms, reports, macros and modules), linked to a back-end
(containing only the tables)? If not, do so.

Once you've done that, create two versions of your front-end: one in 97 and
the other in 2003. (The backend must be left in 97). Each user should have
his/her own copy of the front-end, ideally on their hard drive.