Sick app or sick environments?

[Laurel]

I have an application which runs on 5 different computers. It's been
running OK for a couple of years. But this week, after making some
relatively minor changes, it began to behave "irrationally" on three of the
computers. These computers are the least powerful of the 5. Here are some
of the problems. They are happening on a form that hasn't been edited
recently, but which is more complex than most.

1 - It began executing a function in the query behind the form (formatting a
name) even though no rows were retrieved. Had not done that before, and
failed because the ID was null. I fixed it by adding "If
IsNull(ai_StudentID) Then Exit Function" but then it began failing with
error 2 on one computer, and on another I got error 3. (Note that this
function works fine in other forms, even on the sick computers.)

2 - Dim irst_Students, irst_ClassPeriods As Recordset

 

[ruralguy via AccessMonster.com]

Have you made sure you have no reference problems with these computers?
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

 

[Laurel]

Yes, the reference lists are the same on all the computers.
At first I thought it might be a reference issue and tried removing and
adding them.

 

[Tom Wickerath MDB]

the problem is that Access MDB is unreliable and unusable

 

['69 Camaro]

Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

[David W. Fenton]

Set irst_ClassPeriods = CurrentDb.OpenRecordset(ls_sql)

When this last statement is executed, I get the error "Type
Mismatch". The ls_sql value is "Select * from tblPeriods" a valid
statement.

Has someone perhaps changed the references so that DAO and ADO are
in the wrong order? I note that you don't specify which kind of
recordset. If it's DAO, you should declare it as DAO.Recordset,
particularly in apps with both libraries referenced.

 

[David W. Fenton]

then it began failing with
error 2 on one computer, and on another I got error 3.

Do you know what is reporting these error numbers? In Access those
errors both resolve to "Application-defined or object-defined
error," which would tend to point to a reference problem (i.e., in
some COM component outside of Access itself). This is very
consistent with the DAO vs. ADO problem I suggested in another post.