missing or broken reference 'dao2535.tlb' version 3.5

[Guest]

Over a year a go I got the error "your Microsoft Access database or project
contains a missing or broken reference to 'dao2535.tlb" version 3.5. The
database was original written in Access 97. I was able to use Office 2003 to
convert the data base. This has worked well. However, today I set up a new
computer and loaded Office XP - Including the Access XP. I have 4 computers
with the same version of Access and the computer giving me the problem. The
other 4 continue to have no problem with the Access database. However, the
new installation does. I checked the path and it is the same. Is there an
option in Access I need to set? It can't be the database because it works
fine for the other 4 computers and has for over a year?

 

[Guest]

Check this post on the same subject

http://www.microsoft.com/office/com...rted&mid=03864b3f-40c1-470c-9864-cec0fba411d4

 

[Guest]

But that can't apply because the database was converted over a year ago and
works fine with 4 computers accessing the same database. However, I just
setup a new computer and just loaded Office Xp the same version all the other
computer are using. They don't get any errors? Am I possible missing a .dll
or ???? Options needs to be set in this copy of Access. I have checked the
options against the other copies and seemed to be the same.

 

[Douglas J Steele]

I'd say you were lucky that it worked in the past. That particular reference
(dao2535.tlb) was only intended for use with Access 97. It was for databases
that had been created in a version of Access prior to Access 97 (I think
Access 2.0, but it may also have been for Access 95) and then converted to
Access 97: it ensured backwards compatibility.

It definitely shouldn't be used with Access 2000, 2002 or 2003.

Remove the reference (under Tools | References when you're in the VB
Editor), then compile your application (under Debug when you're in the VB
Editor). If it compiles cleanly, you shouldn't need to do anything else. If
it doesn't compile, hopefully the error message(s) will help pinpoint the
problem. Since your application was written in an older version of Access,
you'll doubtlessly using DAO. Make sure you have a reference set to the
Microsoft DAO 3.60 Object Library.

 

[Guest]

Will I solved the problem. I only had to copy the dao2535.tbl file and put
it in the folder "program file\common files\microsoftshared\dao and it
worked. Guess I am lucky. But you are right - it was written in Access 97
and I used Access 2003 to convert to Windws XP (2002). I didn't write the
orignal database program.

 

[Douglas J. Steele]

You've missed the point that I (and others) made. You should not be using
that reference with Access 2003. It serves no useful purpose, and may
actually cause problems.

 

[Guest]

Actually I didn't miss the point. I completely understand. Howeer, this is
going to be a temp fix. I am working on designing Act database that will
link into Peachtree and replace the Access database all together.

 

[Douglas J. Steele]

Why are you insisting on using an incorrect reference? Just scrap the
reference to dao2535.tbl, and everything should work fine!

 

[megbelgium]

I had the same problem with a database I took over from someone else and I didn't find the reply very useful - how can I Remove the reference (under Tools | References when you're in the VB
>> Editor), then compile your application (under Debug when you're in the VB
>> Editor).if I can't get into the database?
In fact I managed to work round it by opening a new database and importing all the objects from the old one. So far I haven't found any problems.