Options - General

Background Colour

Allows you to select the colour used in many of the AQT windows.

When you click on Other, AQT will show you a color-picker dialog.

Use System Colors

When this option is selected, AQT will use Windows System Colors for many of the elements on the windows.

It is recommended that this option is used if you are using a non-standard Windows Theme, such as High Contrast.

Otherwise it is recommended that this option is not selected.

Alternate Selection Color

By default, when cells are selected in a grid they will be displayed as black on gray. When this option is selected, selected cells will be white-on-blue (which is more inline with the color scheme used in other windows controls).

Prompt before Closing AQT

With this option selected, if you still have a database connection open AQT will prompt you before it closes.

Having this option selected is often useful to prevent inadvertently closing AQT (which can happen if you click on the wrong close button).

Close AQT when all windows are closed

This option specifies whether you want AQT to terminate when all the windows are closed.

Remember user-parms between sessions

Specifies whether you want user-defined parameters saved between AQT sessions. The default is yes.

Save Session on Close

When this option is selected, your AQT session will be saved when you close AQT. The next time you start AQT, your session will be restored.

This option is only used when you close AQT with a number of windows still open. If you close each AQT window then close AQT, the session is not saved (as there are no open windows to save).

External Editor

Use this to specify the external editor to be used when AQT needs to display or edit a file in an external editor.

By default this is Notepad.

Editor Args

This allows you to specify any arguments than need to be passed to the external editor. Code <1> where you want the filename to go.

Example (for Editplus)

-e

-e <1>

This will open the file in an existing instance of Editplus.

If the <1> is not specified it will be assumed to follow the argument.

Attempt to qualify unqualified table names

This is a technical option.

In the Run SQL window and Query Builder windows, it is possible for an unqualified table name to be used. Eg.

Select * from Employee

AQT needs to find the columns for this table. There are two ways AQT can do this:

Use the queries that AQT normally uses for obtaining the columns of a table. The problem with this is that AQT needs to know the table-schema, however this is not given in the query. To deal with this, AQT "guesses" what the schema might be - for instance, it might be the same as the user-id of the person running the query. It has a number of other rules in addition to this.
Do a "prepare" of the query Select * from tablename. This will return the names and data types of the columns, though not fuller information such as the column description. This method will fail if you do not access to the table.

When Attempt to qualify unqualified table names is set, AQT will use the first method. This is the default.

It is recommended that you do not change this option unless you frequently use unqualified table names, and AQT is having trouble finding the columns for the table. There are several circumstances we know of where this might be a problem:

if you use SET SCHEMA, SET CURRENT SQLID (or similar statement) to change your default schema
for Oracle, if you are using Remote Synonyms.
for DB2 for iSeries, if a Library List has been specified on the configuration of the ODBC Datasource

Get Related Table information from User Defined Relationships only

When using the Query Builder or the Link to Related Table feature of AQT, AQT needs to find information on table relationships. It get this from two places:

from the database (eg. foreign key relationships)
from User Defined Relationships

If you do not have any relationships defined to the database, the database query is superfluous and adds unnecessary overhead to AQT. In this case, you may wish to select this option. When this is done, AQT will not query the database for foreign key relationships - it will get related table information from UDRs only.

Use Alternate Password Encryption

This option should only be used in circumstances when the normal password encryption appears not be to be working successfully. This has happened for a few users who are using an unusual character set.

In this case, selecting this option specifies that an alternate method be used to encode the password; this should behave more reliably on a variety of character sets.

Passwords encrypted when this option is selected can not be used by releases of AQT prior to AQT v9.1.0.

Number of searches on Search Table window

This specifies how many searches will be present on the Search Table window.

Database Name

The following three options determine the Name for a database. This is the name the database is identified as on the Window-list bar and other places in AQT.

By default, this will the same as the Datasource name (as appears on the Signon window). However there are options for using a different name.

Show user name as part of database name

When this option is select, the user name will be included as part of the database caption. So instead of the database name appearing as (for instance) Oracle, it will appear as Oracle (system).

This option is useful if you are have multiple connections to the same database, each with a different user-id.

For Oracle, identify database by Server Name

When you sign onto a database, by default the database will be identified within AQT by the Datasource name (this is the name shown on the Signon window).

When this option is select, the database will instead be identified by the Oracle Server name.

Other

This option provides more flexibility than the previous two options, and replaces these two options. In this you can specify in more detail how the database name is to be composed. You specify a mask that consists of text plus some of the following keywords:

<dbs>	The Datasource name
<user>	The signon userid
<userB>	The signon userid enclosed in brackets
<dbname>	The SQL-Server / Sybase the user is signed onto
<instance>	The database Instance identifier. For Oracle, this gives the server name.
<orapriv>	The Oracle privileges (SYSOPER or SYSDBA)
<oraprivB>	As with orapriv but enclosed in brackets

Examples:

<dbs>	This is equivalent to the default name
<dbs> <userB>	This is equivalent to the "Show user name" option
<instance>	This is equivalent to the "Identify database by Server Name" option

You can have different specifications for different database types. The following example demonstrates this:

o:<instance> <oraprivB>;m:<dbs>+<dbname>;<dbs>

In this:

there are three specifications, each delimited with a semicolon
the first two are database-specific specifications (for Oracle and SQL Server). These start with a database identifier followed by a colon.
the last specification is not database-specific. It will apply to those databases which don't match one of the previous entries.

Note that the database identifier is the internal AQT identifer for the database. It can be seen on Help > Database Properties, field Internal AQT Type.

Enable Interface to Document Locator by ColumbiaSoft

When this is checked, AQT will enable the interface to the Document Locator document management system.

This will enable you to save/open AQT files from the Document Locator repository.

This is described in more detail in Document Locator.

Folder for Windows Scheduled Tasks

This is used when creating Scheduled Tasks using AQT's Batch Job feature. It specifies the folder within the Windows Task Scheduler that AQT's scheduled tasks will be created.

If you have multiple AQT users using your machine, you may wish to give each user a different value for this. This will give each user an independent area of the scheduler for their tasks.

Advanced Query Tool

https://www.querytool.com