Expression Builder causes # Error on =[MyField]

[X_HOBBES]

I'm fairly new to Access, let alone Expression Builder. However, it
seems that I'm either doing something really wrong or Access is really
stupid!

I can't reference fields that show up on my report! For example, if I
have a field named MyField on my report, the Control Source has the
value MyField, and it displays the values of MyField properly in the
report. If I try to use an expression as simple as =[MyField], it
fails! I get "# Error" instead of the value.

Am I doing something wrong??? Shouldn't that be a valid expression???
If I'm doing something wrong, please explain what and how I should do
it right.

Please help!

X_HOBBES

[Allen Browne]

If this text box is in the Detail section of the report, try changing its
Name as well. Access gets confused if the control has the same name as a
field, but is bound to somehing else.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"X_HOBBES" <x_******@hotmail.com> wrote in message
news:11**********************@l41g2000cwc.googlegr oups.com...

I'm fairly new to Access, let alone Expression Builder. However, it
seems that I'm either doing something really wrong or Access is really
stupid!

I can't reference fields that show up on my report! For example, if I
have a field named MyField on my report, the Control Source has the
value MyField, and it displays the values of MyField properly in the
report. If I try to use an expression as simple as =[MyField], it
fails! I get "# Error" instead of the value.

Am I doing something wrong??? Shouldn't that be a valid expression???
If I'm doing something wrong, please explain what and how I should do
it right.

Please help!

X_HOBBES

[X_HOBBES]

I found it ACCESS IS STUPID!

As it turns out, if you use the wizard to create a report, or drag
field onto the report, Access will return a "# Error" if you use an
expression. This will happen even if the text box was created
manually, if the field exists elsewhere on the report. In order to fix
this, you need to 1) Delete all occurences of the field on the report,
and 2) create the textbox by hand using the TextBox tool. Then if
you're really lucky, you might be able to use expressions for that text
box.

X_HOBBES

[X_HOBBES]

Thanks for the prompt response Allen. I really appreciate that. It's
very frustrating when certain products have bugs in them that go on for
years without repair -- MS tends to do that a lot.

X_HOBBES