Click the Options button on the Recordset tab to open the Recordset Options
dialog box. Configuring filters and host scrolling behavior gives you more flexibility
in sorting through recordsets when developing a host application model.
- Current record preferences
Configure the options below to describe the properties of the current record
in a recordset. The process of finding the current record is also referred to
as recordset synchronization. When Host Integrator arrives at an entity with
a recordset, it will always indicate the current record is at a record index
of 0, which means before the first record. Any subsequent fetch of data will
then start with the first record and proceed normally.
In some cases, you may not be primarily interested in fetching data. For example,
you may instead want to select a record and navigate to another entity to view
or edit details about it. In these cases, the record that the host claims is
current may be important information for Host Integrator since the host's current
record may not always be the first record. If the host's current record is not
always the first record, the model needs to provide the ability for Host Integrator
to discover which record is current, so Host Integrator can calculate the number
of LineDown or LineUp operations to execute. This is most applicable to character
mode hosts; in block
mode, the host does not typically designate a current record and Host Integrator
can freely choose the record its client desires. Note: The current record
definition defined here can also be used for recordset synchronization
- Use first record on the current screenDefault. Select this
option to assume the first viewable record on the terminal screen as the
host's current record.
- Use current cursor positionSelect this option to designate
the record that contains the cursor as the host's current record.
- Record contains patternSelect a pattern to use as the indicator
of the host's current record location. See the AddressBook entity of the
Pine model for an example.
Tip: On a character mode host, define a pattern with reverse video
in the recordset region, then select that pattern from this list to define
it as a way to discover the current record.
Note: If a connector makes a call that acts on the current record,
such as select or update, Host Integrator will first synchronize the host's
current record to Host Integrator's current record if either of the last
two options listed above is enabled. If this cannot be done for any reason,
an exception will be thrown. To test your recordset before deploying it
to the Host Integrator Server, use the options available in the Test
Recordset dialog box.
If you want Host Integrator to make its current record match that of the
host, use the SetCurrentIndex method and pass the SyncToHost parameter in
your client application. Search for "SetCurrentIndex" in the Host
Integrator API Reference for more information.
- Excluding records
Configure the following options to create recordset filters that remove unneeded
data sent by the host:
- Exclude consecutive repeated recordsSelect this check box
to filter out records that appear at the bottom of one terminal screen and
then repeat at the top of the next screen. Note: If the host you
are creating your model for never repeats records, clear this check box.
- Exclude blank recordsSelect this check box to filter out
blank records that appear on a terminal screen.
- Exclude records matching conditionSelect this option to specify an exclusion condition for the recordset using the condition editor. You can specify a regular expression as part of the condition.
- Scrolling behavior
Configure the following options to indicate in the model
file how the host handles recordsets
that overlap between two screens:
- Host starts each screen with new recordSelect this option
if the host begins each new screen with a new record after scrolling down
to the next screen. This indicates that the result of a PageDown operation
will be a new set of records without any repeated records from the previous
- Host repeats records on new screenSelect this option if the
host repeats records as a way of having continuity between screens when
scrolling is executed. For example, the last record on one screen may appear
as the first record on the next screen after a PageDown operation has been
executed. If the host uses this pattern consistently, select this option
and configure one of the following options in the Repeated record preferences
- Assume __ repeated recordsSelect this option and enter
the number of expected repeated records.
- Dynamically determine repeated recordsSelect this option
to instruct the Host Integrator to recognize repeating records.
- Host overlaps records across screensSelect this option if
the host begins a record on one screen and ends that same record on the
next screen after a PageDown operation has been executed. If the host uses
this pattern consistently, select this option and configure one of the following
options in the Overlapping record preferences box:
- Assume no repeated dataSelect this option if the host
application does not repeat data when a record overlaps from one screen
to the next.
- Dynamically determine repeated dataSelect this option
to instruct the Host Integrator to recognize if there are any repeating
records when records overlap from one screen to the next.
- Skip records not contained on a single screenSelect this
option to instruct the Host Integrator to ignore records that are not
visible on a single screen.
Warning: If you select the Host overlaps records across screens option,
do not select the End of screen is always a delimiter check box under
Record size in the Recordset Layout tab.
© 1999-2007 Attachmate Corporation. All rights reserved.