Printing issues with xMII 11.5

[former_member67937]

For some reason, we have one report (and only one) that is giving us fits when trying to print. The user has JRE 1.4.2_13 installed. When he clicks the print button, IE freezes, and nothing prints. We can go to any other screen, and other report, any other application, and it works fine. It's just with this one particular report. If we install JRE 1.5, it prints fine as well. However, the strange thing is that I can go to a DIFFERENT machine running JRE 1.4.2_13, and that machine prints it OK.

In short, not all machine running JRE 1.4.2_13 have this issue. It doesn't matter when we click the print button, or File | Print, or right-click and print. The result is IE freezes up, and we have to force IE to close.

Has anyone else experienced this?

Thanks,

Todd

[former_member67937]

Thanks for the suggestion.

The query doesn't take very long to run, but it seems silly to have to run the query twice: once for the servlet for the report, and again for the data export, so currently, we're forced to run the query twice, but having it as a link with the contexttype might be a better solution.

[jcgood25]

Todd,

The applets don't use the same builder as the csv output, meaning that they don't receive a xml feed. Raw/binary is what the applets get, whereas the text/csv is actually xml output with a stylesheet.

If the users have the optional need to get csv, then the secondary query should not be that big of a deal, but if it were slow to execute you could consider using query caching for that particular template. This should benefit the text/csv request (because the original template call cached the results).

Regards,

Jeremy

[former_member67937]

No, the purpose of the grid is to allow the user to export the data to Excel via a link on the page. I guess we could move that link outside of the report... but that would be another click of the mouse, and we all know how users want things simple.

[Former Member]

Does the query take awhile to run? You could use the link to link to a URL that calls the query with the ContentType=text/csv option instead of invoking a JS function to call the applet method. Then, you would not need the applet on the page simply to export to csv. Check the help docs to verify the content type url parameter - if its in there.

[former_member67937]

It appears that the issue COULD be because we have an applet on the report that is an iGrid with a width and height of 1. If we expand this out to 4x4, and then use a style of hidden, then the issue goes away. Has anyone experienced anything like this? It seems to happen only with JRE 1.4.2_13.

[Former Member]

Applets. Boo.

[Former Member]

Do you need it to be a hidden iGrid? Can you change it to an iCommand and use getFirstValue()?

[former_member67937]

It appears to be different printers. We tried reinstalling the driver, and that doesn't work, but I wanted to note that everything else works. It's just this report.

[Former Member]

Just this one report on this one computer. What if someone else logs into the same computer? Clear the temporary internet files from IE?

[Former Member]

What about the installed print driver on the troublesome computer? Is it the same version as others?