Non-Printing Fields in Crystal 8.5

[jacck]

Is there some way to display a field in the print preview but not have it appear on the printed report. The only thing i can think is to put it on page 2 of the report and only print page 1 but this is a pain. I just want data to appear for the readers benefit before they print the report but not on the printout itself.

 

[synapsevampire]

You might create a parameter which asks if this is for print and then conditionally suppress the sections that have the display only data based on the response.

So if the displayed data is on thre report footer (going with your page 2 notion), then right clikc the report footer and select format section->X 2 next to suppress and place something like:

{?MyPrintOnlyParm} = "Yes"

There aren't any runtime print only functions, generally people want to print what is displayed.

You posted nothing about the layout of this field, nor it's purpose, so I couldn't advise you specifically.

If you need additional assistance, or in future posts, try to supply technical information specifically stating what you have, where, and what you need.

-k

 

[jacck]

thnks for that. the requirement for the field is to always display data but never print it. if i format the section to suppress based on a runtime parameter then either the field is displayed and printed or not displayed and not printed.

i need some way to display and not print.

is there any way to format a subreport such that it doesn't actually print. or i maybe i could format the page wider than the printout and disply the field to the right.

i also tried to use tooltips that pop-up in the preview screen, and format the text of the tooltip to read the relevant field but its further complicated becaus the field i need to display is a blob.

jacck

 

[lbass]

You could consider using an on-demand subreport for this field or place the field in a hidden section and make it available only upon drill-down. If printing the main report, the drill-down pages or subreport would not print, as long as the current view was of the main report.

-LB

 

[jacck]

tks lb

i tried an on-demand sub-report which looked great but i couldn't access it when i ran the report as a distributed run-time report which this one is. do they work in distributed reports? i will try the hidden section idea and see if the drill-down works - i think drill-down is available in run-time mode.

will let u know

jacck

 

[synapsevampire]

On demands work in distributed reports, proving you use a UNC pathing, and a drill down would also work, however nothing accomplishes what you initially required.

Any of the solutions should get you close, none of them will do precisely what you're after.

-k

 

[jacck]

thanks all

on demand subreport worked perfectly. i overlayed it on an obvious graphic already in the report so users would know where to click and suppressed it so no caption showed. and it worked fine in the distributed version.

like you said synapsev it wasn't precisely what i was after (which would have been a nice little window that popped up in front of the report that went away when the user clicked it) but they only have to click on the graphic look at the subrep preview and then click back on the main page before printing.

still it raised another question which i thought i knew the answer to but obviously don't: what governs a drill-down section.

for example i created a section GH1b to hold this subreport - that didn't give me a drilldown at all. i tried creating GF1b and putting it in there - that gave me a drilldown but the drilldown included GH1, details, GF1a and GF1b. I tried creating Details#b but the drilldown did the same again (GH1, D, GF1a, GF1b).

does a drilldown section need a header, details and footer all of its one?

-jacck

 

[lbass]

Drilldown is for hidden sections. You can adjust whether all headers/footers are shown in file->report options where you can choose to select "Show all headers on drilldown".

-LB

 

[synapsevampire]

Yeahy, the drilldown is for the current reports subsections, not the subreport, if you use drilldown, you shouldn't need a subreport at all, just house the data within the details or sub-groups.

-k