Do I still need in Tools/Reference???

[Bonnie]

Using AXP, recently upgraded from A97. Systems ran
something on our servers that caused an error for my
DB's: ...(filename) contains a missing or broken reference
to the file dao2535.tlb version 3.5.

Deselected reference to "Microsoft DAO 2.5/3.5
Compatibility Library" in Tools. Ran DB on one PC, seems
to work fine.

Systems says I need to deselect that reference on my DB's
to avoid error rather than run a bat file to load the
missing tlb file PC by PC and chance missing someone in
the future. (They know less about Access than I do and I'm
not a programmer so I need outside verification.)

Any reason I shouldn't remove the reference? Is there
another I should select in its place? Currently have the
following selected: VB for Applications, MS Access 10.0
Object Library, OLE Automation, MS VB for Apps
Extensibility 5.0, MS Off XP Web Components, and MS
ActiveX Data Ojbexts 2.7 Library.

Thanks in advance for any help or advice on this issue.

 

[Roger Carlson]

Apparently this application was originally written in Access 2.0 and
upgraded to Access 97. The 97 upgrade wizard put that reference in
automatically. It provided a bridge that translated old Access Basic
commands (that 2.0 used) into VBA commands (that 97 used). It should be
removed and any errors fixed before upgrading to a higher version. If your
application works without this reference, then you needn't do anything
further.

In A97, it was replaced by DAO 3.5 and in 2000 by DAO 3.6. I'm not sure
about AXP, just look for the highest version of DAO that the list has. If
you are not using ADO, you should remove the ActiveX Data Ojbexts 2.7
Library reference. Either that or prefix all of your DAO objects with an
explicit reference to DAO, like this:

dim db as DAO.Database
dim rs as DAO.Recordset
dim qdf as DAO.QueryDef
and so forth.

For more information on this, go here:
http://members.iinet.net.au/~allenbrowne/ser-38.html

 

[Bonnie]

Thank you VERY much for the info.

-----Original Message-----
Apparently this application was originally written in Access 2.0 and
upgraded to Access 97. The 97 upgrade wizard put that reference in
automatically. It provided a bridge that translated old Access Basic
commands (that 2.0 used) into VBA commands (that 97 used). It should be
removed and any errors fixed before upgrading to a higher version. If your
application works without this reference, then you needn't do anything
further.

In A97, it was replaced by DAO 3.5 and in 2000 by DAO 3.6. I'm not sure
about AXP, just look for the highest version of DAO that the list has. If
you are not using ADO, you should remove the ActiveX Data Ojbexts 2.7
Library reference. Either that or prefix all of your DAO objects with an
explicit reference to DAO, like this:

dim db as DAO.Database
dim rs as DAO.Recordset
dim qdf as DAO.QueryDef
and so forth.

For more information on this, go here:
http://members.iinet.net.au/~allenbrowne/ser-38.html

--
--Roger Carlson
www.rogersaccesslibrary.com
Reply to: Roger dot Carlson at Spectrum-Health dot Org





.