Is this possible? Hiding headers if last page contains no rows

Hello everyone. This is my first post here. I have a report that contains a subreport displaying all the aggregate data. My report headings repeat on every page. If my last page contains no rows and only my subreport I do not want the headings to be visible. Now the part I can't get is how to write the condition

if the lastpage.rowcount = 0 then hideHeadings (pseudo)

Is it possible to ask what the rowcount is on the last page? This is the tricky part. Well I'm going to keep trying and if anyone has any solutions I will appreciate it very much.

does ur report contain any tables...?

|||

Yes it does all the data is displayed in a table. However the headings are just text boxes in the header area of the report. If there is a problem with tables I can easily switch to list boxes. Thanks.

|||

to ur table... add a table header row... and let it repeat on each page... so now only if there is data in the next page ur header would show up otherwise no..

Hope this helps.

Regards

KAren

|||

Thank you very much. Something I overlooked. I over analyzed the problem and almost created too much work for myself then what was needed. Now I have 12 reports to do a 2 min fix to each. Thanks again!!!

Is this a security risk?

I'm doing some testing on a vendor’s web site and ran into the error below
. I
told the vendor that displaying this kind of error could give a hacker the
information needed to hack the db or attempt SQL injection attacks etc. (btw
this is a bank). The vendor is telling me that there is no danger in
releasing this information on the web site. I thold them they need to displa
y
something else.
Assuming you or a hacker had this information, company information and the
URL where this error occurred; do you think these pose a security risk?
*** This is the error with the table database and field names changed ****
Insert statement conflicted with COLUMN CHECK constraint
'AColumnCheckConstraint'.
The conflict occurred in database 'ADatabaseName', table 'ATableName',
column 'PaymentAmount'..,
PaymentXML: 10056AWEBWEB01-4858538-14 ... WEBSERVERNAME ...Hi
It is a problem. If I was a hacker, I now have a good load of information to
start hacking with. Based on those names, I can deduce other names.
The toughest part of hacking is getting enough information so that you can
find a hole.This is a Silver platter.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Shark Bait" <SharkBait@.discussions.microsoft.com> wrote in message
news:15B676C1-BAF5-4566-BB1E-31A52B314810@.microsoft.com...
> I'm doing some testing on a vendor's web site and ran into the error
> below. I
> told the vendor that displaying this kind of error could give a hacker the
> information needed to hack the db or attempt SQL injection attacks etc.
> (btw
> this is a bank). The vendor is telling me that there is no danger in
> releasing this information on the web site. I thold them they need to
> display
> something else.
> Assuming you or a hacker had this information, company information and the
> URL where this error occurred; do you think these pose a security risk?
> *** This is the error with the table database and field names changed ****
> Insert statement conflicted with COLUMN CHECK constraint
> 'AColumnCheckConstraint'.
> The conflict occurred in database 'ADatabaseName', table 'ATableName',
> column 'PaymentAmount'..,
> PaymentXML: 10056AWEBWEB01-4858538-14 ... WEBSERVERNAME ...
>|||of Course that is a problem.
PURE Negligence.
Greg Jackson
PDX, Oregon