Programming Guide |
Checks to see if the CONTINUE events are permitted for the current table view
#include <tmusubs.h>int sm_tm_continuation_validity(int report);
report
- Controls whether an error message is generated. If this parameter is non-zero, the message is generated.
- ·
TM_OK
if theTM_CONTINUE_UP
,TM_CONTINUE_TOP
,TM_CONTINUE_DOWN
, andTM_CONTINUE_BOTTOM
events are permitted.
This function is used in the standard transaction models for two-tier applications as part of the transaction manager processing for the
SELECT
andVIEW
commands. It checks the value of thefetch_directions
property for the current table view to see if theTM_CONTINUE_UP
,TM_CONTINUE_TOP
,TM_CONTINUE_DOWN
, andTM_CONTINUE_BOTTOM
events are permitted.If the
fetch_directions
property is specified asDown only-all modes
(PV_CONT_NEVER
), onlyTM_CONTINUE
fetches additional data.TM_CONTINUE_DOWN
is not permitted.If the
fetch_directions
property is specified asUp/Down-view mode
(PV_CONT_VIEW_ONLY
), theTM_CONTINUE_UP
,TM_CONTINUE_TOP
,TM_CONTINUE_DOWN
, andTM_CONTINUE_BOTTOM
events are allowed in addition toTM_CONTINUE
if the current transaction mode isview
.If the
fetch_directions
property is specified asUp/Down-all modes
(PV_CONT_ALWAYS
), theTM_CONTINUE_UP
,TM_CONTINUE_TOP
,TM_CONTINUE_DOWN
, andTM_CONTINUE_BOTTOM
events are allowed in addition toTM_CONTINUE
inview
andupdate
mode. Data must be re-fetched in order for updates to be displayed from the continuation file used with these events.If the table view's
fetch_directions
property is specified asdefault
(PV_CONT_DEFAULT
), the screen's Fetch Directions property is consulted. If the screen's Fetch Directions property is specified asdefault
, this is the equivalent ofDown only-all modes
.