Description of Transaction object properties

Table 12-1 describes each Transaction object property. For each of the ten connection properties, it also lists the equivalent field in the Database Profile Setup dialog box that you complete to create a database profile in the PowerBuilder development environment.

Transaction object properties for your PowerBuilder database interface For the Transaction object properties that apply to your PowerBuilder database interface, see “Transaction object properties and supported PowerBuilder database interfaces”.

For information about the values you should supply for each connection property, see the section for your PowerBuilder database interface in Connecting to Your Database.

**Table 12-1: Transaction object properties**
Property	Datatype	Description	In a database profile
DBMS	String	The DBMS identifier for your connection. For a complete list of the identifiers for the supported database interfaces, see the online Help.	DBMS
Database	String	The name of the database to which you are connecting.	Database Name
UserID	String	The name or ID of the user who connects to the database.	User ID
DBPass	String	The password used to connect to the database.	Password
Lock	String	For those DBMSs that support the use of lock values and isolation levels, the isolation level to use when you connect to the database. For information about the lock values you can set for your DBMS, see the description of the Lock DBParm parameter in the online Help.	Isolation Level
LogID	String	The name or ID of the user who logs in to the database server.	Login ID
LogPass	String	The password used to log in to the database server.	Login Password
ServerName	String	The name of the server on which the database resides.	Server Name
AutoCommit	Boolean	For those DBMSs that support it, specifies whether PowerBuilder issues SQL statements outside or inside the scope of a transaction. Values you can set are: True PowerBuilder issues SQL statements outside the scope of a transaction; that is, the statements are not part of a logical unit of work (LUW). If the SQL statement succeeds, the DBMS updates the database immediately as if a COMMIT statement had been issued. False (Default) PowerBuilder issues SQL statements inside the scope of a transaction. PowerBuilder issues a BEGIN TRANSACTION statement at the start of the connection. In addition, PowerBuilder issues another BEGIN TRANSACTION statement after each COMMIT or ROLLBACK statement is issued. For more information, see the AutoCommit description in the online Help.	AutoCommit Mode
DBParm	String	Contains DBMS-specific connection parameters that support particular DBMS features. For a description of each DBParm parameter that PowerBuilder supports, see the chapter on setting additional connection parameters in Connecting to Your Database.	DBPARM
SQLReturnData	String	Contains DBMS-specific information. For example, after you connect to an Informix database and execute an embedded SQL INSERT statement, SQLReturnData contains the serial number of the inserted row.	—
SQLCode	Long	The success or failure code of the most recent SQL operation. For details, see “Error handling after a SQL statement”.	—
SQLNRows	Long	The number of rows affected by the most recent SQL operation. The database vendor supplies this number, so the meaning may be different for each DBMS.	—
SQLDBCode	Long	The database vendor’s error code. For details, see “Error handling after a SQL statement”.	—
SQLErrText	String	The text of the database vendor’s error message corresponding to the error code. For details, see “Error handling after a SQL statement”.	—