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

Dynamic Report Field Data

P: n/a
Hello,

I have a format issue on an Access 2000 ADP report that I am going to
attempt to explain from a 'ten thousand foot view' :

I have an Access 2000 ADP report that has a SQL Server 2000 Stored Procedure
as its record source. The Proc is called MM_rptTeacherGroupingTest_sp. In
order to help communicate the issue I am having with the report, please take
a look at the following:
http://www.valverde.edu/home/policy/ReportLayout.htm .

The web page first shows the design view of the report. The idea is to show
the T(x)Percent of each StanNum per T(x)Name. The StanNums are grouped by
Strand. The Strands are grouped by Domain. All of this data is based on a
Grade and a Location2 parameter that are sent to the Proc.

The Design view shows only the first three T(x)Name fields and the first
three T(x)Percent fields. The Print Preview shot of the report shows three
T(x)Names and their T(x)Percent values. The results of the report here occur
when a field value called 'TeacherID' is hard coded in the Proc. I did this
just to show a demonstration of what the report might look like.

The query results table represents a sample of the data returned from the
Proc when the 'TeacherID' values are allowed to be dynamic in the Proc (so
the results do not match the Print Preview screen shot). Notice that some of
the T(x)Percent and T(x)Name column pairs in the query results table are
NULL for every record.

Every time the Proc executes, the range of T(x)Percent and T(x)Name fields
starts at T1Percent / T1Name and ends with T14Percent / T14Name (only seven
pairs are shown in the query results table shot). When T(x)Percent column is
null, the matching T(x)Name column will also always be null for every
record. Almost every execution of the Proc will result in null columns in at
least one T(x)Percent / T(x)Name pair.

The problem is, if I simply add all 14 T(x)Name fields in the Location2
header, and all matching 14 T(x)Percent fields in the StanID header, the
null field pairs could leave a lot of empty space in the report.

How can I set up my report so that only the T(x)Name / T(x)Percent columns
that are not completely null appear on the report each time the report is
generated?

If you need to see the code behind the report, please let me know.

Thank you for your help!

CSDunn
Nov 12 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.