Hello Duane
Thanks for the suggestion: I have created a new report
based on exactly the same query, and with all the same
controls, and it works fine! So I guess the original
report was corrupt in some way: and I don't suppose it's
worth my (or anyone else's) time delving into the "why"
issue?
Thanks again for your help.
I do have another problem with reports which I'll outline
here in case you have a ready answer - although I do
understand that a new problem should normally be posted as
such.
[rpt library_refers] is based on [tbl library].
[tbl library] includes the yes/no field [refer].
I want [rpt library_refers] only to display those records
where [refer] = true.
I realise I could do this by basing [rpt library_refers]
on a query and setting [refer] = true as a criteria. But
in fact I need several different reports, with other
criteria, and it seems extravagant to have a seperate
query for each.
I would rather set an 'on open' event e.g.
Me.Filter = "[refer] = true "
Me.FilterOn = True
... but this doesn't work. The crux of the matter seems to
be this:
With the quote marks in place around [refer] = true, the
code seems not to be recognised by access - the
word 'true' is not capitalised and displayed in blue, as
it is if I remove the quotes, and as it is on the 2nd line
Me.FilterOn = True (is this was it known as 'parsing'?).
Without the quotes, the filter doesn't work at all - the
expression isn't recognised and the debugger kicks in.
I would be very grateful if you could tell me what I'm
doing wrong here.
Many thanks
Les.
-----Original Message-----
Do all your reports work this way? You may have a corrupt report. What
happens with a new report that is similar to the existing one?
If you can't resolve this, I would be willing to accept a part of your mdb
for review. You would need to email me directly and ask for instruction on
how to do this since I don't accept emails with attachments without an
agreement (just rules) first.
--
Duane Hookom
MS Access MVP
Hello Duane
No, that's not it either: the underlying query has plenty
of data, and in fact the data displays fine on the
report ... except when I try to join to data fields, like
[field1]&[field2]: that's whan I get #Name (as well as
when I try to print the page number!).
What else could this be?
Thank you for your continued help.
Les.
-----Original Message-----
Check the record source of the report to make sure you
have records to
display. Your symptoms match a report that has no records.
--
Duane Hookom
MS Access MVP
message
Hello Duane
Thanks for your reply ...
... but that's not it - honest!
To try and get to the problem I selected all objects on
the report (using ctrl-A), and deleted them, then
selected
Insert>Page Number from the menu bar: same result.
Hope you can help.
Les.
-----Original Message-----
I expect there might be a field name that is also a
reserved word. By any
chance, do you have a field named [Pages]?
--
Duane Hookom
MS Access MVP
in
message
Hello All
I have a report [rptlibrary] based on query
[qrylibrary].
The report displays all fields OK if I simply drag
them
onto the report from the field list, but if I drag a
text
box from the tools bar and set its data source to,
say ...
=[titlename]
... I get #Name appearing on the report. This is not
because I have got the field name wrong, and it is
not
because the field name is the same as the control
name.
I have also tried starting with the field that has
been
dragged from the field list (which works), then
adding
the
=[ at the beginning and the ] at the end, then
changing
the control's name: this again gives #Name.
It may be coincidence, but if I try printing the page
number (either by selecting Insert>Page Number, or by
setting a text box's data source to =[Page], I again
get
#Name.
Hope someone can help - this has become a real
problem
for
us.
Many thanks
Les.
.
.
.
