By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,163 Members | 976 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,163 IT Pros & Developers. It's quick & easy.

#Name? Error

P: n/a
What does this mean: "#Name?"

I have one user (out of about 80) that is complaining that he gets that in
report text boxes from data that should be coming from an Oracle pass thru.

I couldn't figure out how to google for that string and I get no response
searching the A2K help.

--
Randy Harris
(tech at promail dot com)
Nov 13 '05 #1
Share this Question
Share on Google+
8 Replies


P: n/a
Randy -

In my experience, it seems to mean the report can't find the data
(source) for that specific text box.

Somewhere along the line, a field name is misspelled, a query has had a
field removed, or perhaps a connection is broken.

Do other users running the same report get data instead of #Name, or is
the "complainant" the only user running that particular report? If
other users run the same report and get data, the problem is likely
outside the report or its query. If no other users run that report,
I'd start with the report...

HtH

Patrick

Nov 13 '05 #2

P: n/a
"Patrick A" <me*****@butter.toast.net> wrote in message
news:11*********************@f14g2000cwb.googlegro ups.com...
Randy -

In my experience, it seems to mean the report can't find the data
(source) for that specific text box.

Somewhere along the line, a field name is misspelled, a query has had a
field removed, or perhaps a connection is broken.

Do other users running the same report get data instead of #Name, or is
the "complainant" the only user running that particular report? If
other users run the same report and get data, the problem is likely
outside the report or its query. If no other users run that report,
I'd start with the report...

HtH

Patrick


I'm afraid that's the strange part. The same report works fine for other
users. I don't know what to do!
Nov 13 '05 #3

P: n/a
Randy Harris wrote:
"Patrick A" <me*****@butter.toast.net> wrote in message
news:11*********************@f14g2000cwb.googlegro ups.com...
Randy -

In my experience, it seems to mean the report can't find the data
(source) for that specific text box.

Somewhere along the line, a field name is misspelled, a query has had a
field removed, or perhaps a connection is broken.

Do other users running the same report get data instead of #Name, or is
the "complainant" the only user running that particular report? If
other users run the same report and get data, the problem is likely
outside the report or its query. If no other users run that report,
I'd start with the report...

HtH

Patrick

I'm afraid that's the strange part. The same report works fine for other
users. I don't know what to do!

Then I would debug the problem from his machine.
Nov 13 '05 #4

P: n/a
"Salad" <oi*@vinegar.com> wrote in message
news:rB******************@newsread1.news.pas.earth link.net...
Randy Harris wrote:
"Patrick A" <me*****@butter.toast.net> wrote in message
news:11*********************@f14g2000cwb.googlegro ups.com...
Randy -

In my experience, it seems to mean the report can't find the data
(source) for that specific text box.

Somewhere along the line, a field name is misspelled, a query has had a
field removed, or perhaps a connection is broken.

Do other users running the same report get data instead of #Name, or is
the "complainant" the only user running that particular report? If
other users run the same report and get data, the problem is likely
outside the report or its query. If no other users run that report,
I'd start with the report...

HtH

Patrick

I'm afraid that's the strange part. The same report works fine for other users. I don't know what to do!

Then I would debug the problem from his machine.


How do I go about debugging something like that? There is no error message,
it simply doesn't display the data.


Nov 13 '05 #5

P: n/a
Randy Harris wrote:
"Salad" <oi*@vinegar.com> wrote in message
news:rB******************@newsread1.news.pas.earth link.net...
Randy Harris wrote:

"Patrick A" <me*****@butter.toast.net> wrote in message
news:11*********************@f14g2000cwb.google groups.com...
Randy -

In my experience, it seems to mean the report can't find the data
(source) for that specific text box.

Somewhere along the line, a field name is misspelled, a query has had a
field removed, or perhaps a connection is broken.

Do other users running the same report get data instead of #Name, or is
the "complainant" the only user running that particular report? If
other users run the same report and get data, the problem is likely
outside the report or its query. If no other users run that report,
I'd start with the report...

HtH

Patrick
I'm afraid that's the strange part. The same report works fine for
other
users. I don't know what to do!


Then I would debug the problem from his machine.

How do I go about debugging something like that? There is no error message,
it simply doesn't display the data.


I would open the form in design mode and get the recordsource. I would
then attempt to open it. I would Debug.Print the SQL when he gets that
problem and see if I can run the query. That's where I'd start. I'd
verify some of the problem text boxes are associated with the correct
field. I'd verify he has the same form the others do. If you have
split database check your links.

I really don't know what I'd do...but I'd certainly be testing it out on
his machine that fails and not another machine that works.

Nov 13 '05 #6

P: n/a
On Wed, 20 Apr 2005 15:33:02 GMT, "Randy Harris" <ra***@SpamFree.com>
wrote:
What does this mean: "#Name?"

I have one user (out of about 80) that is complaining that he gets that in
report text boxes from data that should be coming from an Oracle pass thru.

I couldn't figure out how to google for that string and I get no response
searching the A2K help.


Randy,

This might be a wild goose chase, but see if that machine has a
references problem.

mike
Nov 13 '05 #7

P: n/a
Mike Preston wrote:
This might be a wild goose chase, but see if that machine has a
references problem.


Not a wild goose chase at all. From the sounds of the thread with
Patrick and Salad, this would have to be the explanation. PTQs
shouldn't give any #name errors, in my experience; however, you can base
report and form record sources (as well as form combo and list box row
sources) on PTQs but still use Access functions in the control sources
of controls on the report.

What version of Access are you using and does this user have other
versions of Access? If not, are you using A97 and is the problem
machine using win XP?

If so, I'd bet dollars to doughnuts it's a reference problem.
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me
Nov 13 '05 #8

P: n/a
"Tim Marshall" <TI****@PurplePandaChasers.Moertherium> wrote in message
news:d4**********@coranto.ucs.mun.ca...
Mike Preston wrote:
This might be a wild goose chase, but see if that machine has a
references problem.


Not a wild goose chase at all. From the sounds of the thread with
Patrick and Salad, this would have to be the explanation. PTQs
shouldn't give any #name errors, in my experience; however, you can base
report and form record sources (as well as form combo and list box row
sources) on PTQs but still use Access functions in the control sources
of controls on the report.

What version of Access are you using and does this user have other
versions of Access? If not, are you using A97 and is the problem
machine using win XP?

If so, I'd bet dollars to doughnuts it's a reference problem.
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me


I should have given the Access version to begin with. It's an Access 2000
mde, running on XP. It's a good sized app, with about 80 forms, 40 reports
and 20,000 lines of code. The PTQ is the record source for the problem
report. It's strange because some of the data outputs correctly on the
report, others just get that #Name? thing. I believe that the problem has
to be the PTQ. There are a lot of users running the identical same front
end, this is the only with the problem, so I don't think the problem can be
the report itself. I started delving into ODBC driver versions when I found
out this users system is going to be replaced in the next few days. I
figured I'd wait until IT gives him a new system, and see if he still has
the problem. Meanwhile, I've got another user outputting the report to PDF
and emailing to the user with the problem.

Thanks to everyone for the input. I'll let you know if I figure it out.
Nov 13 '05 #9

This discussion thread is closed

Replies have been disabled for this discussion.