S
silva
I'm getting the following error in a field:
#Name?
What am I doing that's causing this error?
#Name?
What am I doing that's causing this error?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
D
Douglas J. Steele
The Help contains the following:
#Error? or #Name? may appear in a control for a number of reasons. To
correct the problem, do the following:
· Make sure that the field specified in the control's ControlSource property
hasn't been removed from the underlying table, query, or SQL statement.
· Check the spelling of the field name in the control's ControlSource
property.
· If you specified an expression in the control's ControlSource property,
make sure that there is an equal sign preceding the expression.
· Make sure that there are brackets around references in expressions to
control or field names that include spaces. For example, to subtract a
Shipped Date field from a Required Data field, enter the following
expression: =[Required Date]-[Shipped Date].
· If you are using one of the built-in functions, make sure that you're
using the right number of arguments, that the arguments are in the right
order, and that you haven't left out any necessary punctuation. To determine
the correct syntax to use, see the Help topic for the function you're using.
· If you are referring to another control, make sure that you're using the
correct syntax.
· Make sure that there isn't a circular reference to a control. For example,
if you specify MyControl in the Name property of a control, and then type
=[A]++[MyControl] in the ControlSource property box for the control,
Microsoft Access can't process the expression.
#Error? or #Name? may appear in a control for a number of reasons. To
correct the problem, do the following:
· Make sure that the field specified in the control's ControlSource property
hasn't been removed from the underlying table, query, or SQL statement.
· Check the spelling of the field name in the control's ControlSource
property.
· If you specified an expression in the control's ControlSource property,
make sure that there is an equal sign preceding the expression.
· Make sure that there are brackets around references in expressions to
control or field names that include spaces. For example, to subtract a
Shipped Date field from a Required Data field, enter the following
expression: =[Required Date]-[Shipped Date].
· If you are using one of the built-in functions, make sure that you're
using the right number of arguments, that the arguments are in the right
order, and that you haven't left out any necessary punctuation. To determine
the correct syntax to use, see the Help topic for the function you're using.
· If you are referring to another control, make sure that you're using the
correct syntax.
· Make sure that there isn't a circular reference to a control. For example,
if you specify MyControl in the Name property of a control, and then type
=[A]++[MyControl] in the ControlSource property box for the control,
Microsoft Access can't process the expression.
A
Anthos
Another cause for this, I have seen, not sure if it is relevant on
forms, maybe more so on reports.
Sometimes when a control has the same name as it's underlaying data
source, the database thinks there is a circular reference.
It is worthwhile changing the names of the controls of your form to a
set standard naming convention, and the underlaying data having a
different name
(i.e. ctlfirstname as the control, and dbfirstname as the source)
Hope I am not leading you up the garden path,
Kind Regards
Anthony Moore
forms, maybe more so on reports.
Sometimes when a control has the same name as it's underlaying data
source, the database thinks there is a circular reference.
It is worthwhile changing the names of the controls of your form to a
set standard naming convention, and the underlaying data having a
different name
(i.e. ctlfirstname as the control, and dbfirstname as the source)
Hope I am not leading you up the garden path,
Kind Regards
Anthony Moore
S
silva
Thank you, guys. I solved the problem. It looked like some bad typing and I
didn't realize it. The expressions couldn't find the bloddy fields due to a
typo.
didn't realize it. The expressions couldn't find the bloddy fields due to a
typo.