You're right this is weird. You may have some corruption developing. Try
decompiling or importing everything into a new mdb file and see if it will
behave. Also, you may have a problem with duplicate names, although why this
would work one time and not the next, I don't know. The duplicate names I'm
referring to are if the control has the same name it as the field it is
bound to.
Example:
Field Name: CircuitQualifier
Textbox Name: CircuitQualifier
Try changing the textbox name to txtCircuitQualifier. Of course, this will
require changing all instances of code that refer to the old name whether in
VBA, queries, or the control source of calculated controls.
Information on decompiling.
http://www.mvps.org/access/bugs/bugs0008.htm
--
Wayne Morgan
Microsoft Access MVP
"Kathy Houtami" <kathy_houtami@hotmail.com> wrote in message
news:55f0be9e.0402021651.b3f381@posting.google.com ...[color=blue]
> Hi there
>
> I've been encountered with weird compile error using Access 97.
>
> The error message is "Member or data member is not found" and it
> highlighted a line of code that has not be changed and has been
> compiled with no error for days.
>
> The code was Me.CircuitQualifier.Requery
>
> It will only compiled if I changed the code to
> Me![CircuitQualifier].Requery
>
> This problem happened to several of my programs. Usually what I do, is
> just to leave the program un-compiled and try to compile it again the
> next day. In 9 out of 10, it will compile fine without changing the
> code at all.
>
> Does anybody know what cause this error?[/color]
