"Method or data member not found"

[GraeagleBill]

A typical problem with Reports is a code reference to a field included in the ControlSource of a report but which DOES NOT have a corresponding bound control in the report design. The workaround for such cases is a simple bound control made non-visible. Like Me.MyField where MyField is the ControlSource of a non-visible text box.



I have such a case where I have 5 non-visible text boxes bound to fields I make reference to in the reports code sheet, all 5 of those code references have been working for years. I just added a 6th text box bound to MyField but I'm still getting the error "Method or data member not found". I've run the ControlSource query independently to ensure that MyField is indeed returned by the query.

Any suggestions?

Thanks,
Bill

[June7]

I know the issue and the solution, always worked for me. Maybe give the textbox a name different from the field it is bound to, like tbxMyField. That's what I always do. Then I reference the textbox name in expressions.

[GraeagleBill]

I'm baffled. I put the references in brackets and the errors went away, i.e., Me.[MyField]. What's baffling is that the none of the other 5 code references are coded with brackets.
Bill

[June7]

Does the field name have spaces or special characters or is a reserved word like Date?

[GraeagleBill]

No. One is "SatDinner" and another just added is "SundayBrunch". No blanks or special characters. I'll try your text box name approach shortly.

[GraeagleBill]

Your text box name approach worked fine. E.g., Me.tbSatDinner blah blah blah where the tb is bound to SatDinner.

[GraeagleBill]

Go figure............ text box name = Text6; Bound to FmType; code reference is Me.FmType. No problem!!! (No other controls bound to that field.)