Connecting to Your Database
Troubleshooting Your Connection

To start ODBC Driver Manager Trace by editing the database profile:

1. Open the Database Profile Setup-ODBC dialog box for the ODBC connection you want to trace.

2. On the Options tab, select the Trace ODBC API Calls check box.

3. (Optional) To specify a log file where you want PowerBuilder to write the output of ODBC Driver Manager Trace, type the path name in the Trace File box

   or

   (Optional) Click Browse to display the pathname of an existing log file in the Trace File box.

   By default, if the Trace ODBC API Calls check box is selected and no trace file is specified, PowerBuilder sends ODBC Driver Manager Trace output to the default SQL.LOG file.

   

4. Click OK or Apply

   or

   Right-click on the connected database and select Re-connect from the drop-down menu in the Database Profiles dialog box.

   The Database Profiles dialog box displays with the name of the edited profile highlighted.

   PowerBuilder saves your settings in the database profile entry in the registry in the HKEY_CURRENT_USER\Software\Sybase\[version]\DatabaseProfiles key.

   For example, here is the relevant portion of a database profile entry for an ODBC data source named Employee. The settings that start ODBC Driver Manager Trace (corresponding to the ConnectOption DBParm parameter) are emphasized.

   DBMS     "ODBC"
   ...
   DbParm   "ConnectString='DSN=Employee;UID=dba;PWD=00c61737',ConnectOption='SQL_OPT_TRACE,SQL_OPT_TRACE_ON;SQL_OPT_TRACEFILE,C:\Temp\odbctrce.log' 

5. Click Connect in the Database Profiles dialog box to connect to the database

   or

   Right-click on the connected database and select Re-connect from the drop-down menu in the Database Profiles dialog box.

   PowerBuilder connects to the database, starts tracing the ODBC connection, and writes output to the log file you specified.

To copy ConnectOption syntax from the Preview tab into your script:

1. On the Options tab in the Database Profile Setup - ODBC dialog box for your connection, select the Trace ODBC API Calls check box and (optionally) specify a log file in the Trace File box to start ODBC Driver Manager Trace.

2. Click Apply to save your changes to the Options tab without closing the dialog box.

3. Click the Preview tab.

   The correct PowerScript syntax for ODBC Driver Manager Trace and other selected options displays in the Database Connection Syntax box.

   The following example shows the PowerScript syntax that starts ODBC Driver Manager Trace and sends output to the file C:\TEMP\ODBCTRCE.LOG.

   // Profile Employee
   SQLCA.DBMS = "ODBC"
   SQLCA.AutoCommit = False
   SQLCA.DBParm = "Connectstring='DSN=Employee',
      ConnectOption='SQL_OPT_TRACE,SQL_OPT_TRACE_ON;
      SQL_OPT_TRACEFILE,c:\temp\odbctrce.log'"

4. Select the SQLCA.DBParm line and any other syntax you want to copy to your script and click Copy.

   PowerBuilder copies the selected text to the clipboard.

5. Paste the selected text from the Preview tab into your script, modifying the default Transaction object name (SQLCA) if necessary.

To start ODBC Driver Manager Trace by setting the DBParm property:

• In your application script, set the SQL_OPT_TRACE and (optionally) SQL_OPT_TRACEFILE ConnectOption parameters to start the trace and to specify a nondefault trace file, respectively.

  For example, the following statement starts ODBC Driver Manager Trace in your application and sends output to a file named MYTRACE.LOG. Insert a comma to separate the ConnectString and ConnectOption values.

  This example assumes you are using the default Transaction object SQLCA, but you can also define your own Transaction object.

  SQLCA.DBParm="ConnectString='DSN=Test;UID=PB;
     PWD=xyz',ConnectOption='SQL_OPT_TRACE,
     SQL_OPT_TRACE_ON;SQL_OPT_TRACEFILE,C:\TRC.LOG'"

To start ODBC Driver Manager Trace by reading DBParm values from an external text file:

• Use the following PowerScript syntax to specify the ProfileString function with the DBParm property:

  SQLCA.dbParm = ProfileString (file, section, variable, default_value)

  For example, the following statement in a PowerBuilder script reads the DBParm values from the [Database] section of the APP.INI file:

  SQLCA.dbParm = ProfileString("APP.INI","Database","DBParm","")

To stop ODBC Driver Manager Trace by editing a database profile:

1. Open the Database Profile Setup - ODBC dialog box for the connection you are tracing.

   For instructions, see Starting ODBC Driver Manager Trace.

2. On the Options tab, clear the Trace ODBC API Calls check box.

   If you supplied the pathname of a log file in the Trace File box, you can leave it specified in case you want to restart tracing later.

3. Click OK in the Database Profile Setup - ODBC dialog box.

   The Database Profiles dialog box displays, with the name of the edited profile highlighted.

4. Click Connect in the Database Profiles dialog box or right-click on the connected database and select Re-connect from the drop-down menu in the Database Profiles dialog box.

   PowerBuilder connects to the database and stops tracing the connection.

To stop ODBC Driver Manager Trace by editing the DBParm property:

• In your application script, edit the DBParm property of the Transaction object to change the value of the SQL_OPT_TRACE ConnectOption parameter to SQL_OPT_TRACE_OFF.

  For example, the following statement starts ODBC Driver Manager Trace in your application and sends the output to a file named MYTRACE.LOG. (This example assumes you are using the default Transaction object SQLCA, but you can also define your own Transaction object.)

  SQLCA.DBParm="ConnectString='DSN=Test;UID=PB;
     PWD=xyz',ConnectOption='SQL_OPT_TRACE,
     SQL_OPT_TRACE_ON;SQL_OPT_TRACEFILE,C:\TRC.LOG'"

  Here is how the same statement should look after you edit it to stop ODBC Driver Manager Trace. (You can leave the name of the trace file specified in case you want to restart tracing later.)

  SQLCA.DBParm="ConnectString='DSN=Test;UID=PB;
     PWD=xyz',ConnectOption='SQL_OPT_TRACE,
     SQL_OPT_TRACE_OFF;SQL_OPT_TRACEFILE,C:\TRC.LOG'"