Access and #Name?

[Nephalim]

First, remind me never to accept an Access project EVER again!

Alright, so it isn't so bad. Except that I CANNOT get my Report to query right using a Crosstab query. Using VBA I was able to accurately get the titles to pring, but not the data. All i get is this stupid symbol: #Name? I want to kill that symbol!

So, what exactly does it mean and how do i fix it?

[biscuitbandit]

just out of curiousity, what section of the report do you have these fields in? i.e. is it report header, page header, detail, page footer or report footer?

it may or may not be the problem but sometimes ive found putting the box in the wrong section will cause problems...

you get the #name symbol usually because access cant find anything to put in that field.

[Nephalim]

It is in the detail section. I ran the query in an SQL query window and it works, it just doesn't want to appear in the report window.

[Tekime]

I believe #Name is displayed when no data was returned from the query for that field. Possibly an err with the query??

I'm working on an Access project now at work too, except one of my priorities is to avoid any macro usage... bleh

[Tekime]

Hrm, I found this in the Access help file:

edit: Heh, now I realize this thread is a week old. Well, I hope youg ot it fixed!

#Error? or #Name? appears in a control on a form or report.
#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 or other record source.


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 Date 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. For more information on referring to controls, click .


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]+[B]+[MyControl] in the ControlSource property box for the control, Microsoft Access can't process the expression.

I don't know if that helps at all...

[Nephalim]

Actually, I just worked around the problem and sort of hacked the report I was working on. No big deal actually - it just ticked me off because I was doing everything right and it just didn't want to create the report.

I've all but finished the database, in fact. The client likes the system very well. Thanks for the heads up, perhaps I'll take another stab at that report...