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.

Hi

Check your references by going into any module then select Tools / REferences
and see if the word MISSING is at the beginning of any reference, if so, simply
click on it to remove it.

I have never seen that 'Missing' you referred to. I
checked and there were none with this in the name
anywhere.

The references were the first thing I checked on the
machines that had the problem. I even made sure they
were in the correct order. (I have had weird things when
references are not in the right order.)

Like I said, I removed the references (working on a
computer that has the problem) and then added them back
in to make sure they were OK.

I knocked out everything but the top 2, VBA and Access
10.0 Obj Lib.

Just for grins, I did a compile with nothing but these 2,
and the compile failed. Then I added the MS DAO 3.6 Obj
Lib and did a compile and it compiled OK.

Then I added VBA Ex 5.3, MS Office 10.0 and OLE
Automation. These 6 are all I need for most of our apps
up here.

The problem seems to be this particular version of the
dll. Only the boxes with this latest version are having
the problem.


>-----Original Message-----
>Hi
>
>Check your references by going into any module then
select Tools / REferences
>and see if the word MISSING is at the beginning of any
reference, if so, simply
>click on it to remove it.
>.
>

I thought that Access 2002 did not like the syntax
of "me.fieldname" anymore. I thought that we were
supposed to use "me!fieldname" or the long way "forms!
formname!fieldname". To my knowledge, I thought the "."
is now used only to reference a property, not a field. I
believe dao350.dll allowed it but not dao360.dll.


>-----Original Message-----
>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.
>
>
>.
>

Interesting. I have my old syntax in code all over the
place and it works OK in earlier versions of the
dao360.dll. I guess we are being forced to change code
one more time. Two-point-Oh to 97 to 2000 to XP. Now a
dll. Drats!

Thanks for the info. I don't get much time for
researching these changes, what with sitting here banging
code all day. And it is always easier to do things the
way you are already used to.

I guess I'll get to put in some extra hours to get things
cleaned up before IT adds that SP4 to all the Win2000
boxes up here. I have a lot of apps floating around the
building. (I have been going back and forth with IT and
they said the SP4 was on its way to all the machines
soon.)

I find myself wondering why SP4 on Windows2000 would have
a more recent version of the dll than either Access SP2
or Windows XP. Hmmm...


>-----Original Message-----
>I thought that Access 2002 did not like the syntax
>of "me.fieldname" anymore. I thought that we were
>supposed to use "me!fieldname" or the long way "forms!
>formname!fieldname". To my knowledge, I thought the "."
>is now used only to reference a property, not a field.
I
>believe dao350.dll allowed it but not dao360.dll.
>
>
>>-----Original Message-----
>>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.
>>
>>
>>.
>>
>.
>

Using . is fine. In fact, I use it exclusively.

--
Paul Overway
Logico Solutions, LLC
www.logico-solutions.com


"bmunny" <(E-Mail Removed)> wrote in message
news:138af01c38475$5cc48950$(E-Mail Removed)...
> I thought that Access 2002 did not like the syntax
> of "me.fieldname" anymore. I thought that we were
> supposed to use "me!fieldname" or the long way "forms!
> formname!fieldname". To my knowledge, I thought the "."
> is now used only to reference a property, not a field. I
> believe dao350.dll allowed it but not dao360.dll.
>
>
> >-----Original Message-----
> >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.
> >
> >
> >.
> >

have you tried decompiling and recompiling the code?
I am running AccessXP SP2 and have never had that problem.

HS

"entodude" <(E-Mail Removed)> wrote in message
news:130c501c38454$ce737be0$(E-Mail Removed)...
> 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.
>
>

"entodude" wrote

> All machines have Access XP. The
> ones with Access SP2 and the ones
> with no SP at all ran OK.

I don't know if DAO360.DLL is updated along with Jet or along with Access,
but I suspect the former. There have been 7 SPs for Jet 4.0, all of which
are, I believe, available either in SP2 or via Office Update in the Windows
Update function. So that is something you might investigate.

But, first, it seems clear that the next step to try is to update to SP2 on
a machine or two that are having the problem and see if that fixes it. After
all, the primary purpose of SPs is to fix problems.

But, the problem could lie outside Access in a shared DLL.

Larry Linson
Microsoft Access MVP

> formname!fieldname". To my knowledge, I thought the "."
> is now used only to reference a property, not a field. I

When you change or set a bound data source for a form
in design mode, Access retrieves all the field name and
field type information for that data source, and you can
use that information to bind controls to fields: if you
look at the control property sheet, you get a drop down
list of available bound fields.

Access ALSO creates a form property for every field
in the data source.

If you have controls on your form (controls in the
control collection of your form), Access ALSO creates
a form property for every control on your form.

Access ALSO creates a form property for module level
variables in the code-behind-form.

If you have a control in the controls collection
with the same name as a field in the fields collection,
the form property will refer to the control rather
than the field.


Creation of these properties by Access only happens
when the form is in design mode, so if you change
the record source of a form at runtime, the form
properties do not change.

Also, if you are using integrated SourceSafe with
Access, the form properties are not created correctly.


These form properties will appear as auto-complete
values while coding behind the form if you type 'Me.'

We use this syntax extensively, and have not yet
had any problem with A2K/SR7. We have not tested
SR7 with A2002.

(david)



"bmunny" <(E-Mail Removed)> wrote in message
news:138af01c38475$5cc48950$(E-Mail Removed)...
> I thought that Access 2002 did not like the syntax
> of "me.fieldname" anymore. I thought that we were
> supposed to use "me!fieldname" or the long way "forms!
> formname!fieldname". To my knowledge, I thought the "."
> is now used only to reference a property, not a field. I
> believe dao350.dll allowed it but not dao360.dll.
>
>
> >-----Original Message-----
> >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.
> >
> >
> >.
> >

> I don't know if DAO360.DLL is updated along with Jet or along with

dao360.dll 3.60.6508.2 is in Jet SR7 and Win2K SR4.

3.60.3714.5 was in Jet SR6.

I don't know which, if any, of the other Jet SR7 files were in Win2K SR4.

(david)


"Larry Linson" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "entodude" wrote
>
> > All machines have Access XP. The
> > ones with Access SP2 and the ones
> > with no SP at all ran OK.
>
> I don't know if DAO360.DLL is updated along with Jet or along with Access,
> but I suspect the former. There have been 7 SPs for Jet 4.0, all of which
> are, I believe, available either in SP2 or via Office Update in the
Windows
> Update function. So that is something you might investigate.
>
> But, first, it seems clear that the next step to try is to update to SP2
on
> a machine or two that are having the problem and see if that fixes it.
After
> all, the primary purpose of SPs is to fix problems.
>
> But, the problem could lie outside Access in a shared DLL.
>
> Larry Linson
> Microsoft Access MVP
>
>