I have an HTML Composer page that references a procedure. The procedure takes WFFMT as one of its parameters, and permitted formats include PDF and HTML.

The procedure (A) contains a link to a second procedure (B). If I click A's link I successfully navigate to B (within the HTML iframe), but then I have no easy way of getting back to A unless I regenerate the original report.

If the output format is HTML then in certain browsers I can right-click and choose to navigate back within the iframe that wraps the output - this uses the browser's own cached copy of the output and displays fine. However, in PDF I don't have this option.

I thought I could get around this problem with a button that has an onclick action to navigate back through the iframe's history, e.g.

 
<input type='button' value='Back' onclick='frame_name.history.back()'> 

But this seems to request a fresh copy of the PDF, and as no POST parameters are provided I only get 'No query information to decode'.

I could link this 'back' button to the HTML page's main 'run' button, or include a link back to A within B, but I'm sure there should be a way to navigate back to the original report without regenerating it.

Any suggestions on this problem are very welcome.

This message has been edited. Last edited by: Kerry,

Tom, before trying anything else, verify the following: Do you get the 'No query information to decode' message while running the report in MRE or B.I. Dashboard? In my experience, this only occurs when running the report from Dev Studio, which the end-user will not be doing.

Thanks for the suggestion, but while Firefox does behave as expected IE (9) still shows the 'No query information to decode' message. I think I was testing as you suggested, I went directly to the html page via URL so the browser shouldn't have any interaction with Developer Studio.

p.s. you're my WebFocus hero for this rant