Specifies whether InfoMaker should trim trailing spaces from data values retrieved from the following datatypes: Char, Char for Bit Data, VarChar, and VarChar for Bit Data.
ASE, SYC Sybase Adaptive Server Enterprise
DIR Sybase DirectConnect
I10 Informix
IN9 Informix
JDB JDBC
ODBC
O90 Oracle9i
O10 Oracle 10g
SNC SQL Native Client for Microsoft SQL Server
TrimSpaces=value
Parameter |
Description |
|---|---|
value |
Specifies whether InfoMaker should trim trailing spaces from data of type Char, Char for Bit Data, and VarChar for Bit Data. Values are:
|
TrimSpaces=0 (O90, O10, SNC and IN9) or TrimSpaces=1 (DIR, ASE, and SYC). For JDBC, the default values depend on the PBTrimCharColumns value in the registry. For ODBC, the default values depend on the PBTrimCharColumns value in the PBODBnnn.INI file. (If the PBTrimCharColumns keyword is missing for a particular database connection, the default value for the ODBC interface is TrimSpaces=0.)
By default, InfoMaker trims spaces from the following datatypes: Char, Char for Bit Data, VarChar, and VarChar for Bit Data.
ODBC database interface
Some ODBC drivers, such as ASA, trim trailing spaces before
the data reaches the fetch buffer—even when TrimSpaces
is set to 0.
If your DBMS makes a distinction between Char data with trailing
spaces and Char data without trailing spaces when evaluating a WHERE clause
expression, you might receive the message Row
changed between retrieve and update when your form’s update
properties are set to “Key and updateable columns.” To
prevent this, change your form’s update properties.
In embedded SQL, you can check
Sqlca.Sqlnrows after each update to determine if the update took
place. Avoid using Char data columns in the WHERE clause
of an UPDATE or DELETE statement
when TrimSpaces=1.
To specify that InfoMaker should not trim trailing spaces, clear the Trim Trailing Spaces In CHAR Data check box on the Syntax page in the Database Profile Setup dialog box.
