Select the desired database engine to connect. QLR Manager will only display the database engines that have the necessary PHP connection extensions already installed.

Enter a User ID that has already been established in the database to be accessed.

This is the Password for the database User ID entered.

Some database configurations require that a database name be provided at connect time. If the Database input field is present on the  Connect  panel, then a valid entry is required.

The Systems Administrator can manually edit the qlr.ini file to change the value of "DBlogin", such as DBlogin = inventory, to preset the database that is selected at log on.

The DB server is the server where the database resides in relation to QLR Manager. For MySQL, it is generally "localhost", meaning that the database resides on the same server as QLR Manager.

In MySQL or PostgreSQL, it might be necessary to specify a port if the database's default port is not used. This is accomplished by adding the port to the end of the server reference, such as localhost:3305.

For Oracle database connections, this is the TNS alias that is created in Oracle's TNSnames.ora file which is used to reference the desired database and server.

A selection list of available servers can be added by the Systems Administrator. This is accomplished by logging into QLR Manager using the master QLR Manager ID and creating an Input Control called "qlr_server_list". This feature is available in the Enterprise Edition only. The set of server choices can be entered as a List of values, using the text :: value format, such as:

local::localhost,
china::9.9.14.201,
denmark::23.45.98.2

This will trigger a select list to appear below the DB server input field. The User can then choose an entry from the list, or type a new entry into the DB server field.

This selection determines what page set of functions the User wishes to access.

Queries · Layouts · Reports allows for the creation of queries and layouts, and viewing, e-mailing, or downloading the output. It also provides a menu listing all the macros and queries previously saved by the User ID, and those that have been built into a menu and shared by other users. The Start-up preference selection will direct the logon to the desired panel and save this preference as a cookie on the local PC.

Macros · Menus · Forms allows for the creation of macros, menus and forms, and provides the capability of previewing the output.

User ID Admin and Tools provides a set of panels to create input controls, export QLR data for import into another QLR instance, load data from various source file types into a database table, and set authorities for User IDs.

Note: What the User ID actually sees after logon to any of the above functions is determined by the authority granted the ID through User ID Admin. For example, a Restricted User will not see the header tabs for  Query  Query and  Layout  after logon, only  User Menu  and  Report . If a Restricted User attempts to select the option for Macros · Menus · Forms, they will receive a message that their User ID is not authorized. An Advanced User could have access to both page sets and all functions. These authorities are normally set by the Administrator logging on with the master ID and password established when QLR Manager was initially installed, but can also be delegated to other IDs through User ID Admin.

Clicking the  Log off  button takes the User back to the  Connect  panel and erases all reports from the User's current session. The User must log on again in order the gain access to QLR Manager.