|
|
|
|
|
These options govern how data is to be displayed when you run a query or display a table.
This specifies how null values are displayed.
Whether numeric values are left or right justified in the grid.
These options specify how Date, Time, DateTime and Timestamp columns are displayed. Enter a format using a combination of the letters: y (year), M (month), d (day), H (hour), m (minute) and s (second) plus any delimiting characters (such as -,: or /).
Examples:
MM-dd-yyyy will display as 12-31-2001dd/MMM/yyyy will display as 31/Dec/2001HH.mm.ss will display as 15.32.58Timestamps and Datetime columns display as: Date Format + “ “ + Time Format.
You can read a more detailed discussion about Date and Time columns.
The date format MUST include the following specifications: yyyy, MM or MMM, dd.
The time format MUST include the following specifications: HH, mm, ss.
For Oracle, the NLS_DATE_FORMAT will be changed to what you specify for the Date Format.
These options specify how Informix date / time literals are to be specified. This must match the format specified in the DBDATE or GLS_DATE environment variables. If AQT were smarter, it would be able to automatically pick up the DBDATE / GLS_DATE values; however it cannot do this, so this literal format need to be specified here.
These options need to be specified as described in Format of Date/Time Columns, except that the mmm specification is not valid.
These options only need to be specified for Informix. For all other databases, the format of the date / time literals are hard-coded in AQT (see Date and Time columns for more on this). For Informix, the way in which date and time literals are specified is not fixed, but depends on the DBDATE or GLS_DATE environment variables.
Binary Columns are columns which can contain non-ASCII data (in DB2 these are defined as CHAR FOR BIT DATA, in Oracle they are defined as RAW, in Sybase and SQL Server they are defined as BINARY). This also includes BLOB and VARBINARY columns.
AQT can display binary data in two formats:
The default mode for AQT is smart. In this mode, AQT will display the binary columns in either ASCII mode or hex mode depending on the contents of the column – eg. it is displayed in ASCII mode if the column contains only displayable characters, otherwise it is displayed in hex mode.
When AQT is displaying data in hex mode, this option will add a space between byte values. This makes the hex value more easy to read. Example:
This specify how many bytes of hex data AQT will display.
The option only applies to DB2 z/OS and DB2/iSeries binary columns. This includes character columns defined as FOR BIT DATA and VARBINARY.
For normal character columns, Ebcdic - Ascii translation is done by DB2/Connect or DB2 CAE. However this is not done for columns defined as FOR BIT DATA, as these may contain binary information for which conversion is not required. However, if you have any normal text in these columns, they will display in AQT in Ebcdic format, and so will be unreadable.
When this option is selected, AQT will check whether binary columns contain Ebcdic data (it does this looking for Ebcdic characters in the first 20 bytes of the column). If so, the column value is converted from Ebcdic to Ascii, and so will display correctly in AQT.
Notes:
This option allows character columns that contain ascii 0 characters to be displayed fully in AQT. Normally, such strings are truncated at the ascii 0 character - this is because text-boxes (and other Windows components) interpret the ascii 0 as an end-of-string delimiter. To circumvent this, when this option is selected, AQT will scan all strings being displayed and replace any ascii 0 characters with spaces. This enables the full string values to be displayed.
In the or as box, you can specify which character is to be used to display x'00' characters. By default this is a single blank; you can specify another character here.
This option also applies to data returned in OUT and INOUT parameters of Stored Procedures.
When this is specified, AQT will replace all unprintable characters with the specified string. Unprintable characters are those in the range ascii 0 to ascii 31.
If the replacement string contains a colon, the ascii code will be replaced there. For instance, when $(:) is specified, an ascii 10 will be replaced with $(10).
This option will override the Display x'00' characters as spaces option.
This option will not be used for LOBs which are written to files with the Write LOBs to files option.
This option will have a small impact on performance, so should not be used unless necessary.
When you specify this option, every time you run a saved-query, AQT will check whether there is a layout-file for that query. If so, AQT will format the data as per the specifications saved in the layout-file. This is discussed in more detail in Saving / retrieving the display Layout.
When you specify this option, every time you display a table, AQT will check whether there is a layout-file for that table. If so, AQT will format the data as per the specifications saved in the layout-file. This is discussed in more detail in Saving / retrieving the display Layout.
