scratch
Last Activity: Sep 8 '14, 08:41 PM
Joined: Sep 6 '14
Location:
-
@Bike: The form is bound to a recordset with City in it. When the field City is entered, the display shows the correct data. -
@NeoPa - Entering the single field as you typed (and with or without brackets) displays the correct data.
Also entering a literal string expression works (e.g. ="A" & " " & "B" yields a result of "A B".) However, entering =[Field1] & " " displays #Error.
FWIW the field is named City, not Field1. I'm using that as an example.
Thank you for your...Leave a comment:
-
Thank you both for your assistance.
I need to clarify: I've tried with both the leading equals and without. Trying to combine terms in an expression seems to create the error.
In the property sheet under control source when I enter Fields1 or [Field1] it displays correctly. However, when I enter =[Field1] the text box displays #Error.
I'm stumped. I appreciate any help.Leave a comment:
-
Yes, but the problem only began occurring once I upgraded.
Suggestions to avoid this error?Leave a comment:
-
Control Source syntax error after upgrading to 2013
Hi. I'm accustomed to using programmed fields in Access 2010 but after changing to 2013 my expressions result in a syntax error. For instance, using this expression as my control source in the property sheet:
[Field1] & " "
... where Field1 is a field in my table pops up a dialog box warning me of a syntax error, followed by a second pop-up with the message "Microsoft Access can't find the field...
No activity results to display
Leave a comment: