It appears ScriptX is unavailable or has failed to install.

Has the Infobar appeared?

If you are using Internet Explorer 6 or later on Windows XP SP2 or later then the Explorer Information bar may appear while trying to install ScriptX, it looks like this:

If the bar has appeared, follow the instructions: click on the bar and then select Install ActiveX Control...

Are you an administrator?

ScriptX is code that requires you have administrator rights on your machine in order to install it successfully.

If you are not an administrator, please contact your administrator and ask them to install ScriptX for you.

Printing HTML Documents or Reports with ScriptX

This discussion assumes that you are familiar with the basic principles of controlling printing with ScriptX.

In the 'classic' usage of ScriptX to provide an enhanced printing experience of HTML documents in Internet Explorer, the printing UI is included in the page to be printed. The samples section discussing reports illustrated a number of techniques for providing report menus and 'batch' printing of reports, including the preferred method of leveraging the (licensed) printHtml() method.

The printHtml() method implements its own queue and caches printing parameters (including printer to use and so on) - documents are downloaded and once the download is complete, the document is printed.

In its default usage, users must wait for the entire queue to download and print before navigating away from the page. However, the OwnQueue() method moves the printHtml queue to its own independent process and users are free to get on with their work.

However, there is a price to pay for this flexibility when dealing with dynamic server side systems that rely upon maintenance of session information and in particular those that rely upon the use of cookies to maintain that information.

In its default usage, the printHtml() queue shares session information transferred to the browser by the server with the Internet Explorer browser session. For example, session cookies are shared and the server will believe that requests made by the queue are in the same session as previous requests from the browser and so, for example, log-on information etc is 'preserved'.

When OwnQueue has been called, a new independent process is created and no session information (cookies) from the parent browser are transferred. Requests made by the queue to the server will therefore appear to be from a new browser session and any log-on information that is persisted by cookies will have been 'lost'. A typical result of this is that rather than the expected report being produced, a logon page or site default page is displayed (the requested report page will have determined that the session is not logged on and will perform a redirect to the default/logon page).

Illustration

The cookie for this browser's session with the server is: [910aa702-1b2f-4371-b5aa-0ff389863829, written at: 12/3/2008 8:06:11 PM]

Using printHtml(), we can print a page via the same session, and so the session cookie printed will be the same as displayed above.

Print - once you have printed, the print type - in-process or out-of-process, will stay the same, use Refresh to switch usage