DRILLTHROUGH and NOSPLIT don't mix?

In a compound PDF report with drill-through, where the lower report uses NOSPLIT, the DOWN link from the upper report sometimes misses the mark, pointing to the page before the start of the targeted section.

In computing the link points, WF apparently count the portion of the preceeding page that is left blank because of the NOSPLIT feature (the pont where the new section would have started if not for NOSPLI) to be part of the new section of output.

Anyone else run across this problem?

- Jack Gross
WF through 8.1.05

Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005

susannah

Expert

posted

Hide Post

here's all i can find in the doc
"Not all line types are appropriate for placement of a Drill Through hyperlink. For example, if a page break occurs on a BY field that is also a Drill Through link, each page heading is clearly associated with a value in that field. However, if a page break occurs because of page overflow, avoid placing a Drill Through link in a heading. Similarly, subheadings, subfootings, subtotals, and recaps are associated only with the values of particular BY fields"
but i'm sure you've already read this. probably wrote it!
so NOSPLIT must just not really be enough to truly overcome the deep-seeded desire to page-break...
hence the problem.
hmm.

In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID

Posts: 3811 | Location: Manhattan | Registered: October 28, 2003

Ignored post by susannah posted

Show Post

j.gross

Virtuoso

posted

Hide Post

Susannah --

I interpret those caveats as refering to the sending page, the place where the hyperlink is imbedded -- if the link is in output other then a DATA instance, the sort-column values (and hence the target) that WF associates with it may not be what meets the eye.

My issue concerns the target page, when the sending location's values are unambiguous. If there is whitespace left at the bottom of the page because of a NOSPLIT sortbreak, I think of those lines as no-mans-land, belonging neither to the old section nor to the new one -- but the process in WF that sets of the hyperlink thinks of those blank lines as the opening lines of the new section. Result is that the link leads to page 4, when the visible content of the associated section starts on page 5.

I opened a case (50292549) and provided a repro.

Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005

Ignored post by j.gross posted

Show Post

susannah

Expert

posted

Hide Post

i hear you.
Let us know what resolution you get, if any, would you?
You know how much Waz likes to work magic w/ PDFs...maybe if he has his ears on...he'll work out a solution.

In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID

Posts: 3811 | Location: Manhattan | Registered: October 28, 2003

Ignored post by susannah posted

Show Post

Please Wait. Your request is being processed...