If upgrading from an earlier version, see migration information.

If upgrading from an earlier release within the same version, see product upgrade.

In order to run QLR Manager, you must have a product license file. Prior to buying QLR Manager, we urge everyone to take advantage of our FREE 30 day trial of the Enterprise Edition. This will ensure it runs correctly in your environment and the product meets your expectations. If you first request a trial license and later wish to buy QLR Manager, you simply upgrade the trial license. To receive a license, you must first create a user account so we can e-mail your license file. A trial or purchased license can be obtained from our Purchase page.

To install the QLRlicense.inc file, simply copy the file into the same directory where QLR Manager is installed, which is the same directory where the file qlrmanager.html is located.

A license will entitle you to free upgrades and fixes within the same version. We don't release a new version until we incorporate significant new function and features. Upgrades to new versions are steeply discounted for existing license holders.

A migration is necessary when the underlying QLR Manager database tables, or data in those tables, must be updated. A migration is always necessary when upgrading from one major version to another, e.g. version 4.1.5 to version 5.0. In addition to updating the QLR database tables, the migration will copy your existing queries, layouts, etc. to the new version.

If you wish to erase your existing queries and layouts, or this is a new installation, simply access install.html with your browser and choose the New Installation option to install the product.

A product upgrade occurs when a more recent release is available for the same product version number, e.g. upgrading from version 4.0 to version 4.1.5. The same QLRlicense.inc file will work with all releases of the same major version number. A FREE Upgrade pack is normally provided on our Downloads page when an upgrade is available for the current version. The Upgrade pack will contain the files to be replaced in your QLR Manager installation to upgrade to the latest release.

Note: It is not usually necessary to run install.htm for an upgrade within the same version. You are simply replacing the existing QLR Manager files on your server.

An upgrade differs from a migration to a new version of the product, i.e. version 4.1.5 to version 5.0.

If your server is configured to use index.php, you can access QLR Manager by simply entering the path name. If you do choose to change the name of qlrmanager.html, index.php should also be edited to reflect the new file name.

With the release of MySQL 4.1, a new method of password hashing was introduced and continues to be used. When using PHP version 4.x, QLR Manager is unable to recognize these passwords unless they are normalized to the pre-4.1 password style. This is critical because QLR Manager requires that an existing user ID and password be provided to perform the product installation. The user ID performing the installation must be using the old style password. This does not appear to be an issue when using PHP 5.0 or newer.

In order to change the password for the ID that will perform the install, you should issue the following MySQL command:

SET PASSWORD FOR 'some user'@'some host' = OLD_PASSWORD('existing password');
Example: SET PASSWORD FOR 'conor'@'localhost' = OLD_PASSWORD('guinness');

Note: In addition to normalizing the password for the user ID that will perform the installation, the password for any user ID that will be accessing QLR Manager must be changed as well.

The following is an example of a mixture of new style (longer) and old style (shorter) encrypted passwords.

  select host,user,password from mysql.user

After issuing the MySQL command to change to old style password:

  SET PASSWORD FOR 'conor'@'localhost' = OLD_PASSWORD('guinness');

The contents of the user table would appear as follows:

More information can be found at: http://dev.mysql.com/doc/mysql/en/password-hashing.html.

A phpinfo.php file is provided as part of the QLR Manager install package and will be located in the main install directory. Executing this file from the browser, e.g. my_domain/qlr_directory/phpinfo.php, will return information about the server configuration. Scroll down to the section entitled Configuration PHP Core to view the php.ini settings.

Suhosin is an add-on protection system for PHP installations. The presence of a Suhosin Patch can be detected by executing phpinfo.php and searching the page for "suhosin". The default values for suhosin.post.max_vars and suhosin.request.max_vars limit requests to 200 variables. These settings are not sufficient to run QLR Manager and it is recommended these values be increased to 2000 variables.

In general, yes you can. Some browsers behave differently than others. The most stable browser for using these buttons is Internet Explorer. It can be very useful to use Back and Forward when paging back and forth between page sets in a large report. Be aware that you may page back to a screen that is in a different "page state". An example might be that you ran a query to generate a report, paged back to the query page, and then try to return to the report page via the Report tab. The query page may not recognize that a report exists, because you have paged back to its state prior to running the query.

No. You will be able to install, or upgrade your version of QLR Manager without loosing any of your data. If you decide to Purchase a non-expiring license. you simply upgrade your trial license.

QLR Manager displays reports in blocks of pages, or "page sets". The number of rows in a page set is defined as the reportRows value in the qlr.ini file created when QLR Manager is installed. If the block size is set to 500 (default value), then 500 rows can be displayed at one time. QLR Manager can create up to 1,000 page sets for a report. Therefore, using this reportRows setting, 500,000 rows of data can be displayed. If queries do generate more than the allowable maximum rows, you can either use the "Group" Action in the Layout panel to compress rows, or Group the data in your query with the SQL "Group By" function. Navigation links (First, Back, More, Last) are provided above the report output to move between page sets.

The value established during installation and recorded in the qlr.ini file becomes the default for the installation. There is also a "Max displayed rows" control in the Report Body section of the Layout panel that will override the installation default. If this value is increased, more report rows will be displayed per page set. The compromise is the time your browser will take to render larger page sets. The slower rendering speed can be very noticeable with slower network connections.

The Max displayed rows value can be increased to produce one continuous set of report pages. This may be desirable to print the output or to produce a PDF. If the Layout is saved as the same name as its associated query or wizard, it will be automatically applied when the query, wizard or menu item is executed.

The probable cause is that your database engine is not running on your server. Check to make sure you have started the database engine.

alter session set nls_date_format = 'DD-MON-YY HH24:MI:SS';

Since QLR Manager supports batch query processing, multiple commands can be placed into this query, separated by a semicolon(;). Each User ID may have a "user session" query. This technique also works for MySQL commands, such as "set".

This may be due to a memory limitation in PHP. QLR Manager attempts to alter memory allocation at runtime for memory intensive operations, such as creating charts. If your browser still hangs or produces incomplete output, this is probably because QLR Manager was unable to increase the memory allocation. See optimal php.ini settings for more information.

QLR Manager Version 5.1.2 introduced the capability of setting the Max displayed rows in the Report Body section of the Layout panel. This provides a method of overriding the installation default for the total number of report rows that will be displayed for each block of pages, or "page set". By entering a value that is greater than the total numbers of rows expected to be produced by the query, one continuous set of pages will be produced. Using the Print displayed output option in the Report tools pop-up, the entire report can be printed or sent to a PDF writer. Saving a layout with the same name as its associated query or wizard will automatically apply the layout when the query is executed.

When sending the output to a PDF writer such as Adobe Acrobat or CutePDF (available free from www.cutepdf.com), it is usually desirable to produce the PDF in full color. There is a Print black & white control in the Report Body section of the Layout panel that must be deselected. In addition, the default installation for most browsers prevents printing background colors to conserve ink. The printing selections for your browser may have to be changed to print to a PDF writer in full color. More information about these browser settings can be found in our User's Guide.

Mailing labels can be printed from Microsoft Word using an imported CSV file downloaded from QLR Manager. Begin by authoring a query to select the desired address records from your database. Include the appropriate columns in the report to generate mailing labels such as, name, street, city, state, and zip code. Generate the report and launch Report Tools. Open the section for Download as Data File and select "Include column headers" and "CSV". Click Create and download the file to your local PC.