Programming Guide

Fetches the next set of information from the database

int sm_tm_command ("CONTINUE [ tableViewName [ tableViewScope ] ]");

tableViewName

The name of a server view in the current transaction. This parameter is case sensitive.

If tableViewName is specified, the command is applied according to the tableViewScope parameter. (Since the entire table view tree might not be included, this is known as a partial command, and sm_tm_command sets TM_FULL to 0.) The specified table view must either be a server view or be the server view to which the desired table view belongs.

If tableViewName is not specified, the command is applied for each table/server view, starting with the root table view. This is known as a full command, and sm_tm_command sets TM_FULL to 1.

tableViewScope

One of the following parameters, which must be preceded by a table view name.TV_AND_BELOW which applies the command to the specified table view and all table views below it on the tree. If no parameter is specified, the transaction manager acts as though TV_AND_BELOW was supplied. BELOW_TV which applies the command to the table views below the specified table view. TV_ONLY which applies the command to the specified table view only. SV_ONLY which applies the command only to the table views of the specified server view.

CONTINUE (not available in Web applications or three-tier processing) fetches the next set of information from the database. If there are no additional rows, this command has no effect.

CONTINUE does not set the transaction mode but requires view or update mode. A partial CONTINUE command is also permitted in new mode.

Push buttons and menu selections for the CONTINUE command can choose to set the class property to continue_button. By default, continue_button is active in view and update modes.

If your screen has multiple table views, the transaction manager issues a DBMS CONTINUE for the specified table view and any table views linked to it via server links. This displays the next set of rows for that server view. Then SELECT or VIEW processing is done for any additional child table views.

If your screen has multiple table views and you want to fetch data for only one table view, use FETCH instead of CONTINUE.

If the setting of the Fetch Directions property, as discussed in the CONTINUE_DOWN command, permits the CONTINUE_DOWN command to be executed, the data displayed by this command for the specified server view can come from a continuation file. The warnings for CONTINUE_DOWN then apply.

Use CONTINUE after SELECT or VIEW which generate a database query and display the first set of query results.

The following requests can be generated by the CONTINUE command to ascertain whether the changes from the previous command have been saved and, if desired, to discard those changes:

• TM_PRE_CLOSE (described under CLOSE)

• TM_CLOSE (described under CLOSE)

• TM_QUERY (described under CLOSE)

• TM_DISCARD (described under CLOSE)

• TM_POST_CLOSE (described under CLOSE)

The following requests can also be generated:

• TM_FETCH (described under FETCH)

• TM_PRE_SELECT (described under SELECT)

• TM_SELECT (described under SELECT)

• TM_POST_SELECT (described under SELECT)

• TM_PRE_VIEW (described under VIEW)

• TM_VIEW (described under VIEW)

• TM_POST_VIEW (described under VIEW)

If TM_VIEW or TM_SELECT for a parent table view returns no data, TM_CLEAR requests are generated for all subordinate table views, but not for table views at the same level of the tree. TM_CLEAR requests are described under CLEAR.

---

---