Step 5: code your application to use the user object – PB Docs 125

What you have done so far

In the previous steps, you defined the GIVE_RAISE remote
stored procedure as an external function for the u_trans_database standard
class user object. You then specified u_trans_database as
the default global variable type for SQLCA.
These steps give your PowerBuilder application access to the properties
and functions encapsulated in the user object.

What you do now

You now need to write code that uses the user object to perform
the necessary processing.

To code your application to use the user object:

1. Open the object or control for which you
   want to write a script.

2. Select the event for which you want to write the
   script.

   For instructions on using the Script view,
   see the PowerBuilder Users Guide.

3. Write code that uses the user object to do the
   necessary processing for your application.

   Here is a simple code example that connects to an Oracle database,
   calls the GIVE_RAISE stored procedure
   to calculate the raise, displays a message box with the new salary,
   and disconnects from the database:

   PowerBuilder

   // Set Transaction object connection properties.

   1	// Set Transaction object connection properties.

   PowerBuilder

   SQLCA.DBMS="OR7"

   1	SQLCA.DBMS="OR7"

   PowerBuilder

   SQLCA.LogID="scott"

   1	SQLCA.LogID="scott"

   PowerBuilder

   SQLCA.LogPass="xxyyzz"

   1	SQLCA.LogPass="xxyyzz"

   PowerBuilder

   SQLCA.ServerName="@t:oracle:testdb"

   1	SQLCA.ServerName="@t:oracle:testdb"

   PowerBuilder

   SQLCA.DBParm="sqlcache=24,pbdbms=1"

   1	SQLCA.DBParm="sqlcache=24,pbdbms=1"

   1

   PowerBuilder

   // Connect to the Oracle database.

   1	// Connect to the Oracle database.

   PowerBuilder

   CONNECT USING SQLCA ;

   1	CONNECT USING SQLCA ;

   1

   PowerBuilder

   // Check for errors.

   1	// Check for errors.

   PowerBuilder

   IF SQLCA.sqlcode <> 0 THEN

   1	IF SQLCA.sqlcode <> 0 THEN

   PowerBuilder

         MessageBox ("Connect Error",SQLCA.SQLErrText)

   1	      MessageBox ("Connect Error",SQLCA.SQLErrText)

   PowerBuilder

         return

   1	      return

   PowerBuilder

   END IF

   1

   END IF

   1

   PowerBuilder

   // Set 20,000 as the current salary.

   1	// Set 20,000 as the current salary.

   PowerBuilder

   DOUBLE val = 20000

   1	DOUBLE val = 20000

   PowerBuilder

   DOUBLE rv

   1

   DOUBLE rv

   1

   PowerBuilder

   // Call the GIVE_RAISE stored procedure to

   1	// Call the GIVE_RAISE stored procedure to

   PowerBuilder

   // calculate the raise.

   1	// calculate the raise.

   PowerBuilder

   // Use dot notation to call the stored procedure

   1	// Use dot notation to call the stored procedure

   PowerBuilder

   <span>rv = SQLCA.give_raise(val)</span>

   1	<span>rv = SQLCA.give_raise(val)</span>

   1

   PowerBuilder

   // Display a message box with the new salary.

   1	// Display a message box with the new salary.

   PowerBuilder

   MessageBox("The new salary is",string(rv))

   1	MessageBox("The new salary is",string(rv))

   1

   PowerBuilder

   // Disconnect from the Oracle database.

   1	// Disconnect from the Oracle database.

   PowerBuilder

   DISCONNECT USING SQLCA;

   1	DISCONNECT USING SQLCA;

4. Compile the script to save your changes.

An actual script would include error checking after the CONNECT statement, DISCONNECT statement,
and call to the GIVE_RAISE procedure.
For details, see “Error handling after
a SQL statement”.