Name Error Microsoft Access
Contents |
of #name access 2013 Use Forms: Resolve #Name error in a ms access #name in report form/report Author(s) Dev Ashish (Q) Why do I get a #NAME error for
#error Access
a calculated control on a form or a report? (A) You are probably using the same name for a calculated text box as one of the terms
Access Control Source #name?
in the expression. In the following example, Access produces a #NAME error if you enter the expression in a control named City, State, or ZIP: =[City] & "", "" & [State] & "" "" & [ZIP] This creates a circular reference that may be resolved by changing the name of the control that contains this expression to something (anything) other than City, State, or ZIP. © 1998-2010, Dev Ashish & Arvin Meyer, All rights reserved. Optimized for Microsoft Internet Explorer
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 21 Oct 2016 01:00:40 GMT by s_wx1196 (squid/3.5.20)
help? Post your question and get tips & solutions from a community of 418,595 IT Pros & Developers. It's quick https://bytes.com/topic/access/answers/514816-reports-unbound-fields-name-error & easy. Reports with unbound fields #Name? error P: 16 beat1078 I have a report that I create using unbound text boxes to link to an open form. When you click on a cmdbutton on the form the report is supposed to print out information from the form. It works fine until I close the database and restart it. That name error is when I receive the #Name? error. Nothing that I have tried works to resolve the issue. My text box names do not include references to the information I am requesting in the control source (txtNme for field name and =reports![ReportName]![FieldName] for control source) If anyone can help I would greatly appriciate it. --Jason Jul 22 '06 #1 Post Reply Share name error microsoft this Question 3 Replies 100+ P: 179 comteck This can be caused when the name that you supplied as the source of the control's value is not valid. You use the ControlSource property to specify the source of the control's value. For example, you might have misspelled the name, or the source might have been renamed or deleted. You may also see #Name? in a control if you place an expression in the control's ControlSource property and you insert a space before the equal sign that starts the expression. Make sure that all the fields specified in your ControlSource actually exist in the underlying table or the RecordSource.. As well, if you're using an expression in the ControlSource, make sure there's an equal sign in front of the expression. Hope this helps. comteck Jul 22 '06 #2 reply P: 16 beat1078 Comteck, I triple checked my expression in the controlsource. It reads exactly as this: =Forms!frmInputForm![PERSON SSN] No space in front of the equal sign. I even used the expression builder to make sure I didn't mistype anything. When I st