Working form has stopped working: Repost and Update

I repeat below my previous post on this problem. I have still
not solved it, but I have at last found time to try again...

<<<<<<<<<<<<
The form Chooser has worked without problems for about a year.
It suddenly stopped working in November.

It was written for Access2003, but I don't spend much time at the
facility where it's used, so I took it over to the local university
to try to run it. I found that the university had updated to
Access2007

This message appeared when I opened the database:

"Missing or broken reference to dao2535.tlb version 3.5"

The Chooser form did open and display its lists of agencies and
employees, but when I tried to select from either list I got this
message:
"can't compile module. Compile error: can't find
project or library"

The debugger indicated that this happened in function AgencyChoice.

Using the References line of the Tools menu I found the missing
reference listed as

"MISSING:Microsoft DAO2.5/3.5/Compatibility Library
Location: C:/Program files/Microsoft Shared/DAO/dao253"

Is this simply a library missing from the university's libraries
or is this problem related to the form's failure to open on the
system where it's being used?

I asked someone at the site of use to provide more detail on the
problem there. Here is his summary:

"We have several computers at work that fail to run the form.
Microsoft puts up a crash window and offers to repair the
database. This cycles with no other message.
The test computer has XP and Access 2003. A year ago the program
ran with no problem on this and other computers, so we suspect
Microsoft updates may have created the problem.

A laptop computer runs the program with no problem. It has been
totally rebuilt with XP and Access 2007.

I found that the dao253.tlb was an older version on the work
computer that fails. I replaced it with a newer version from
the laptop. There was no change..

I have inventoried the References listed in the Visual Basic window.
There are four libraries mentioned. Below I have summarized the
References and the file associated with each reference.

"A" is the work computer. "B" is the laptop.

(Two VBA references are listed because the window does not
clarify the ending of the name.)

Available References

Visual Basic for Applications
C:\Program files\common files\Microsoft shared\VBA\VBA6\

vbe6.dll A 5/9/07 B 10/22/07
vbe6ext.olb A 7/3/03 B 10/22/07

Microsoft Access 11.0 Object Library
C:\Program files\Microsoft Office\Office 11\MSACC.OLB
A 7/30/03
Microsoft Access 12.0 Object Library
C:\Program files\Microsoft Office\Office 12\MSAAC.OLB
B 8/24/07
[Using the 12.0 Object Library didn't help. --trl]

OLE Automation
C:\Windows\system 32\stdole2.tlb
A 4/13/08
B 2/28/06 (Actually older)

Microsoft Active X Data Objects 2.1 Library
C:\Program files\common files\system\ado\msado21.tlb
A 4/13/08
B 2/28/06 (Actually older)

Microsoft DAO 2.5/3.51 Compatibility Library
C:\Program files\common files\Microsoft Shared\DAO\dao2535.tlb
A5/15/98
B same (I moved copy from B to A)"

The form fails so catastrophically that I can't use a step through
process with the debugger to trace what's happening. Can you tell me
how to begin to look for the problem?


I took Lyle Fairfield's suggestion and removed the reference
flagged as missing when I tried to run on the University's
system, and sure enough, it now runs fine there, and on the
laptop.

But at the site where it's used any attempt to run the form
responds with the message "Microsoft Access has encountered
a problem and needs to close. We are sorry for the inconvenience."

The form is called from a menu form and the debugger shows me
that it dies as I single step from the code line

DoCmd.Openform stDocName,,,stLinkCriteria
The debugger shows that stDocName is 'frmChooseAgency'
stLinkCriteria is ''

The list of forms in the mdb does include 'frmChooseAgency'.
I get the same 'sorry for the inconvenience' message if I try
to open the form in design view or if I try to do a 'save as'
of it or if I try to print its information. So I have no idea
how I can begin to debug it. Can someone please help?

thanks, --thelma

.

Relevant Pages

  • Re: cycle through a table
    ... Doug Steele, Microsoft Access MVP ... "Phil" wrote in message ... >> program and object libraries that provide functionality that may be ... References to the specific library files, ...
    (microsoft.public.access.modulesdaovba)
  • Working form has stopped working
    ... Microsoft updates may have created the problem. ... I have inventoried the References listed in the Visual Basic window. ... There are four libraries mentioned. ... Microsoft Access 11.0 Object Library ...
    (comp.databases.ms-access)
  • Re: Recommended order of VBA References in Access
    ... If precedence or speed are required, then the order of these references is ... An easy way to tell if the necessary libraries are ... > My applications do not use any Active X components. ... See http://www.Access.QBuilt.com for Microsoft Access tips. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Compatibility issue?
    ... You actually stated that you checked the same libraries were installed, I was referring to checking that they have been referenced in the project. ... What might be happening is that object references, names changing, cell contents may be creating conditions that cause your code to fail. ... Microsoft Office 10.0 Object Library ... Arlette...there are no other files associated with this spreadsheet and it ...
    (microsoft.public.excel.programming)
  • Re: Cannot Set recordset in A2003
    ... Make sure that the Microsoft ActiveX Data Objects 2.5 Library is ... positioned below the DAO library or that it is turned off. ... > Microsoft Access 11.0 Object Library ... >> You don't mention which libraries you have a reference to. ...
    (microsoft.public.access.formscoding)
Loading