E
entodude
I think we have stumbled on a bug in the dao360.dll
installed with Windows 2000 SP4.
The version installed is ver 3.60.6508.2 (older version =
3.60.3714.5); date is
06/19/2003 (older version = 10/4/2001);
We are getting the error in Access XP: "Run-time
error '2424': The expression you entered has a field,
control, or property name that [app name] can't find."
In the code is a line:
strCompany = Me.txtCompany
We chased this one all over the place. I could not
repeat the error in my dev version of the app. I watched
the users who were getting the message and they were all
doing things the way they were supposed to. Some people
had the problem, others didn't.
I forced the references on the machines with the problems
by deleting the references and then linking back to the
libraries. I figured this would force an update in the
registry and fix it. Didn't help.
So we logged on to boxes all over the floor and found
that the problem appears to be related to this particular
library, dao360.dll.
All machines have Access XP. The ones with Access SP2
and the ones with no SP at all ran OK.
The Windows 2000 SP3 and Windows XP machines ran fine.
The Windows 2000 SP4 boxes had the problem.
After gathering info on the file versions and dates, it
looks like this is the problem. I have found nothing
related to this in the KB.
installed with Windows 2000 SP4.
The version installed is ver 3.60.6508.2 (older version =
3.60.3714.5); date is
06/19/2003 (older version = 10/4/2001);
We are getting the error in Access XP: "Run-time
error '2424': The expression you entered has a field,
control, or property name that [app name] can't find."
In the code is a line:
strCompany = Me.txtCompany
We chased this one all over the place. I could not
repeat the error in my dev version of the app. I watched
the users who were getting the message and they were all
doing things the way they were supposed to. Some people
had the problem, others didn't.
I forced the references on the machines with the problems
by deleting the references and then linking back to the
libraries. I figured this would force an update in the
registry and fix it. Didn't help.
So we logged on to boxes all over the floor and found
that the problem appears to be related to this particular
library, dao360.dll.
All machines have Access XP. The ones with Access SP2
and the ones with no SP at all ran OK.
The Windows 2000 SP3 and Windows XP machines ran fine.
The Windows 2000 SP4 boxes had the problem.
After gathering info on the file versions and dates, it
looks like this is the problem. I have found nothing
related to this in the KB.