AggrFuncs=avg(),count(),max(),min(),sum()
Functions=curdate(),curtime(),dayofmonth(),hour(),left(),length(),minute(),month(),second(),substr(),year()

[DB2CS_FUNCTIONS]
AggrFuncs=avg(),count(),max(),min(),sum()
Functions=blob(),char(),date(),day(),days(),decimal(),digits(),double(),float(),hex(),hour(),integer(),length(),microsecond(),minute(),month(),nullif(),posstr(),raise_error(),second(),substr(),time(),timestamp(),translate(),value(),vargraphic(),year()

[DEFAULT_FUNCTIONS]
AggrFuncs=ave(),count(),max(),min(),sum()

[SearchServer_FUNCTIONS]
Functions=relevance()

[SYBASE_FUNCTIONS]
AggrFuncs=ave(),sum()
Functions=substr()

[TEXT_FUNCTIONS]
Functions=concat(),curdate(),curtime(),database(),dayofmonth(),dayofweek(),left(),ltrim(),length(),locate(),lcase(),mod(),month(),right(),rtrim(),substring(),ucase(),user(),year()
AggrFuncs=avg(),count(),max(),min(),sum()

; ********************************************************************
; Special data type information
; special data type information is dbmstype = pbtype
;         where dbmstype is the data source-dependent data type name and pbtype
;         is the PowerBuilder string representation of the PB data type
; ********************************************************************

[WATCOM_SPECIALDATATYPES]
SpecialDataTypes='tinyint=DBI_TINYINT=-6'

[ACCESS_SPECIALDATATYPES]
SpecialDataTypes='text=DBI_TYPEVCHAR=12,memo=DBI_TYPESTRINGLONG=-1;0'

[DBASE_SPECIALDATATYPES]
SpecialDataTypes='char=DBI_TYPEVCHAR=12,float=DBI_TYPEDECIMAL=100;10,numeric=DBI_TYPEDECIMAL=3;5,memo=DBI_TYPESTRINGLONG=-1;0'

[HYPERSTAR_SPECIALDATATYPES]
SpecialDataTypes='MONEY=DBI_TYPEMONEY=100'

[IDMS_SPECIALDATATYPES]
SpecialDataTypes='char=DBI_TYPECHAR=1'

[INFORMIX_SPECIALDATATYPES]
SpecialDataTypes='MONEY=DBI_TYPEMONEY=100,SERIAL=DBI_TYPEINT=101'

[PARADOX_SPECIALDATATYPES]
SpecialDataTypes='FORMATTED MEMO=DBI_TYPEBLOB=100,GRAPHIC=DBI_TYPEBLOB=101,OLE=DBI_TYPEBLOB=102,CURRENCY=DBI_TYPEFLOAT=103'

[QE_BTRIEVE_SPECIALDATATYPES]                                                                   
SpecialDataTypes='AUTOINCREMENT(2)=DBI_TYPESINT=100,AUTOINCREMENT(4)=DBI_TYPEINT=101,MONEY=DBI_TYPEDECIMAL=102;10,ZSTRING=DBI_TYPEVCHAR=103,LOGICAL(2)=DBI_TYPEBIT=104,BFLOAT(4)=DBI_TYPEFLOAT=105,BFLOAT(8)=DBI_TYPEFLOAT=106,NUMERICSTS=DBI_TYPEDECIMAL=107;10,'

[QE_NETWARESQL_SPECIALDATATYPES]                                                                        
SpecialDataTypes='AUTOINC=DBI_TYPESINT=100,AUTOINC(4)=DBI_TYPEINT=101,MONEY=DBI_TYPEDECIMAL=102;10,ZSTRING=DBI_TYPEVCHAR=103,LOGICAL(2)=DBI_TYPEBIT=104,BFLOAT=DBI_TYPEFLOAT=105,BFLOAT(8)=DBI_TYPEFLOAT=106,NUMERICSTS=DBI_TYPEDECIMAL=107;10,BIT=DBI_TYPEBIT=108,LVAR=DBI_TYPESTRINGLONG=109'

[REDBRICK_SPECIALDATATYPES]
SpecialDataTypes='time=DBI_TYPETIME=101,timestamp=DBI_TYPETIME=102'

[SQLBASE_SPECIALDATATYPES]
SpecialDataTypes='char=DBI_TYPECHAR=1,number=DBI_TYPEFLOAT=100'

[SYBASE_SPECIALDATATYPES]
SpecialDataTypes='timestamp=DBI_TYPETIMESTAMP=100,money=DBI_TYPEMONEY=101'

; ********************************************************************
; DBMS Driver / DBMS Settings
; 
; Powerbuilder takes advantage of extended capabilities of ODBC drivers
; and navigates around shortcomings by utilizing pbodb70.ini file
; entries in the data source, DBMS Driver, or DBMS section.  If no
; sections exist for a particular connection then Powerbuilder runs
; as an ODBC compliant client and extensions that might be available
; cannot not be utilized.
;
; The search algorithm for the entries is:
;      IF section and entry for are present current datasource
;      THEN use entry value
;      ELSE IF section corresponding to DBMS_Name Driver_Name exist
;      THEN use entry value if it exist
;      ELSE IF section corresponding to DBMS_Name exist
;      THEN use entry value if it exist
;
; If PowerBuilder is search for SQL syntax and no entry is found in
; the above search Powerbuilder searches the syntax section which
; corresponds to the current datasources SQL Grammar conformance level.
;
; SECTION Headings - DataSource_Name (None are in ini file by default
;                    but if you need to override the more general
;                    setting of DBMS_Driver or DBMS_Name you would put
;                    in a data source specific section
;
;                  - DBMS_Name Driver_Name (Driver_Name is stripped of
;                    .dll extension) 
;
;                  - DBMS_Name (DBMS name returned by the SQLGetInfo call)                                       
; 
; Entries which appear under these section headings include:
;
;BlobSegmentSize=4096 - buffer size to use for SQLPutData when updating
;   blob fields, default is 4096
;Block=nnn - default is 1000,  maximum # of rows to retrieve with extended 
;   fetch if SQLExtendedFetch is supported for a data window
;DelimitIdentifier='NO' - do not delimit identifiers in SQL syntax,
;   default is YES if datasource returns a identifier delimiting
;   character
;ForeignKeyDeleteRule=Option text (option key word), option text
;   (option key word) - specify up to 3 options for foreign
;   key constrain action on delete of primary key,  if the (option
;   key word ) is not found then the option text is assumed to be
;   the key word  
;IdentifierCase=3 - overrides SQLGetInfo Identifier case value
;   4 - case insensitive, 3 - mixed case, 2 - lower, 1 - upper
;IdentifierQuoteChar='<quote_char>' - overrides quote char returned
;   by SQLGetInfo for SQL_IDENTIFIER_QUOTE_CHAR, value can be overridden
;   by the DBParm entry IdentifierQuoteChar
;InsertBlock=nnn - # of rows to block for insert if bind parameters supported,
;   DEFAULT is 100
;PBCatalogOwner='Powerbuilder_Catalog_Owner'- Powerbuilder catalog tables
;   are referenced with this owner, default if this entry is not found
;   is the signon user
;PBConCatIndex='NO' - do not use concatenated indexes, used when
;   creating PowerBuilder catalogs, default is 'YES'
;PBDateTime='name of section which contains date, time, and datetime
;            formats'
;PBDateTimeInvalidInSearch='YES' - data windows does not use datetime
;   in where criteria, default value is 'NO'
;PBDefaultValues='comma separated list of database default value keywords'
;PBDefaultCreate='YES' - database default value supported in CREATE TABLE
;  statement, DEFAULT is NO
;PBDefaultAlter='YES' - database default value supported in ALTER TABLE
;  statement, DEFAULT is NO
;PBDefaultExpressions='YES' - expressions allowed in database default value,
;  DEFAULT is NO
;PBDWDynamic='NO' - data windows needs second connect to handle retrieve
;   as needed data windows, default is 'YES'
;PBEscapeChar='NO' - do not escape meta characters _ or % when making
;   ODBC catalog API calls, default is 'YES'
;PBFileManager='YES'    - driver is a file manager i.e. Dbase, used when
;   creating PowerBuilder catalogs, Default is 'NO'
;PBFunctions='name of section which contains native function names'
;PBMaxBlobSize='32767' only used by MS SQLServer for read blob 
;   statement option
;PBMaxTextSize='32767' only used by MS SQLServer for Text fields 
;   limit      
;PBNoCatalog='YES' - do not use Powerbuilder catalogs, default is 'NO'
;PBNoRequiredFields='YES' - do not set not null attribute when creating
;   or altering table definitions, default is 'NO'
;PBNonStdChars='- +....' allow up to 15 non standard SQL identifier
; characters to be treated as valid chars in identifiers.  Default is
; no non standard chars
;PBObjectIDs='YES'- use SQLServer/Sybase object ids for Powerbuilder
;   catalog entities, default is 'NO'
;PBParseProcs='NO' - do not parse execute procedure stmts from script painter
;PBPrimaryKeyName='YES' - primary key needs constraint name. Default is NO
;PBQualifierIsOwner='YES' - use the table qualifier returned by SQLTables
;   as the qualifier for the table name,  default is 'NO' use the table
;   owner returned by  SQLTables as the qualifier for the table name
;PBQualifiersOnDesc='YES' - the column name returned by SQLDescribeCol
;   may be fully qualified, Default is NO
;PBReadOnly='YES' - Powerbuilder runs in read only mode, Powerbuilder
;   catalogs are accessed if they exist but not updated, default is 'NO'
;PBSyntax='name of section which contains SQL syntax'
;PBSpecialDataTypes='name of section which contains special data types'
;PBSupportBindSelect='YES' - support use of bind variables in select
;  criteria.  The default is yes. Note if the data source does not support
;  the SQLDescribeParam function then PowerBuilder will not attempt to use 
;  bind variables. This setting can be overridden by disablebind in DBParm
;PBSupportBindUpdate='YES' - support use of bind variables in insert, update,
;  and delete SQL statements.  The default is yes.  See PBSupportBindSelect
;  for comments
;PBSupportDBBind='YES' - support use of bind variables in rpc and pipeline
;  SQL statements.  The default is yes. Note if the data source does not support
;  the SQLSetParam function then PowerBuilder will not attempt to use 
;  bind variables;
;PBSystemOwner='System_Owner' - entities returned by SQLTables which
;   match this owner are treated as system tables
;PBTableDot=0  - a decimal number,  if 0 then table names which include
;   a "." are excluded from the table list, otherwise the table are 
;   listed
;PBTableOwner='NO' - do not qualify table names, default is 'YES'  
;PBTimeInvalidInSearch='YES' - data windows does use time in where
;   criteria; default is 'NO'
;PBTrimCharColumns='YES' - trim trailing blanks after fetching character
;   data, default is NO
;PBTrimCatCharColumns='YES'- trim trailing blanks on character data 
;   returned from catalog API calls, default is 'NO'
;PBUseProcOwner='YES' - include procedure owner name when the call escape sequence
;   is generated for a stored procedure, DEFAULT is 'NO',  Can be overridden
;   by DBparm entry PBUseProcOwner
;SQLSyntaxQualifiers=1 - only qualify sql identifiers with one qualifier,
;   default is 0 which means use the PowerBuilder default rules to qualify
;   identifiers
;SQLSrvrTSName='YES' - A column named "timestamp" is treated as a special SQLServer
;   like timestamp, DEFAULT is NO
;SQLSrvrTSQuote='YES' - Put SQLServer like timestamp value in single quotes,
;   DEFAULT is NO
;SQLSrvrTSDelimit='YES' - delimit the SQLServer like timestamp column name timestamp,
;   DEFAULT is NO
;SQLSrvrTSPrefix='cc' - 2 character prefix for SQLServer timestamp values,
;   DEFAULT is NO
;
; The Syntax sections identified by the PBSyntax entry values are used
; to define SQL syntax substitution patterns for SQL Data definition
; statements generated by PowerBuilder painters. Substitution variables are
; preceded by an &, elements which are exploded in another entry are preceded
; by ::, and repeating entities are followed by [, entity ]...  If a 
; substitution variable is not included in the pattern then the generated
; does not contain the substitution value.  For example if &TableName is
; not in the CreateTable pattern then the generated syntax does not contain
; a table owner qualifier.
;
; Syntax entries and their substitution variables include:
;
;AddColumn=
;   &TableOwner.&TableName ::AddColElement[, ::AddColElement ]... - add column
;   to an existing table syntax
;AddColElement=
;   &ColumnName &DataType &Null
;AlterForeignKey=
;   &TableOwner &TableName &KeyName (&ColumnName[,&ColumnName]...) &RefTableName
;AlterPrimaryKey=&TableOwner &TableName (&ColumnName[,&ColumnName]...)
;CreateForeignKey=
;   &KeyName (&ColumnName[,&ColumnName]...) &RefTableName
;CreateIndex=
;   &UNIQUE &IndexName &TableOwner &TableName (::ColumnIndex[, ::ColumnIndex]...)'
;ColumnIndex= 
;   &ColumnName &Descending or &Ascending - if &descending is used then
;   PowerBuilder allows you to create indexes with descending order otherwise
;   only ascending indexes can be generated  
;CreatePrimaryKey= 
;   (&ColumnName[,&ColumnName]...)
;CreateTable= 
;   &TableOwner &TableName (::ColumnElement[, ::ColumnElement]...)
;ColumnElement='
;   &ColumnName &DataType &Null or &NotNull     - if &Null is used then
;   every column that allows nulls will have the NULL keyword,  if 
;   &NotNull is used then any column that does not allow nulls will
;   have the NOT NULL keywords for that column definition 
;DeleteColumn=
;   &TableName ::DeleteColElement;
;DeleteColElement=
;   &ColumnName
;DropForeignKey=
;   &TableOwner.&TableName &KeyName   
;DropIndex=
;   &TableName &IndexName'
;DropPrimaryKey=
;   &TableOwner.&TableName 
;DropTable=
;   &TableOwner &TableName
;DropView=
;   &TableOwner &TableName
;GrantTablePrivilege=
;   &Privilege[,&Privilege]... &TableOwner &TableName &UserName[,&UserName]...
;ModifyColumn=
;   &TableName ::ModifyColElement
;ModifyColElement=
;   &ColumnName &DataType
;PBOuterJoin=
;   &FirstJoin &OuterJoin1 &Operator &OuterJoin2 &SecondJoin' - native
; outer join syntax. If PBOuterJoin is not defined, PB assumes the data source 
; supports ANSI outer joins (as defined by the ODBC specs). 
; &OuterJoin1 and &OuterJoin2 represent the keywords where the type of join
; will be substituted. If the outerjoin is on the FirstJoin, the operator
; defined by PBOuterJoinOperator is substitued in &OuterJoin1. If the outerjoin
; is on the secondjoin, the operator defined by PBOuterJoinOperator is 
; substitued in &OuterJoin2. The &Operator is currently the '=' sign.
;PBOuterJoinOperator='*'
;PBSelectProcSyntax=
;   &ObjectOwner &ObjectName - SQL syntax to retrieve procedure definition text
;PBSelectViewSyntax=
;   &ObjectOwner &ObjectName - SQL syntax to retrieve view definition text
;RenameColumn=
;   ::RenameColElement - rename column syntax
;RenameColElement=
;   &TableName.&OldColumnName &NewColumnName
;RenameTable=
;   &OldTableName &NewTableName - rename table syntax
;RevokeTablePrivilege=
;   &Privilege[,&Privilege]... &TableOwner &TableName &UserName[,&UserName]...
;ShowPlanSyntax=
;   &sqlstmt - the sql statement that you want execution plan info for, it
;   must return 1 column dingle row char data formatted as you want it 
;   displayed
;
; The Datetime sections referenced by the PBDateTime entry value define
; the formats for date, time, and datetime formats that Powerbuilder uses
; in SQL syntax these datatypes.  If no Datetime section is specified
; Powerbuilder uses the DEFAULT_DATETIME section.  For maximum portability
; use the ODBC escape sequence which is the default.  For maximum performance
; use the native forma