|Contents:||Main||Chapter||See Also:||Getting Started Manual||Advanced User Manual|
Block properties are stored in two locations:
Since these properties are stored in the Form file, they apply only as it is used on a particular form.
(Required) This is the .01 field of the block multiple of the page multiple of the Form file (#.403). This field is a pointer to Block file (#.404).
(Required) The Block Order determines the order in which users traverse fields on a page when they press <PF1><PF4> to go to the next block or press the Enter/Return key to move from the last field on one block to the first field on the next. When the user first reaches a page, ScreenMan places the user on the block with the lowest Block Order number.
Type of Block
(Required) The Type of Block property can be either "DISPLAY" or "EDIT."
EDIT blocks allow fields to be changed by the user and DISPLAY blocks allow fields to be displayed but not changed by the user. Adding an EDIT block to a form enables the editing of any data dictionary fields placed on the EDIT-type block. Fields in a DISPLAY block are read-only.
When you first add a block to a form, you enter the properties for the block, including the type of block it is. You can also edit the properties of the block later. See the "ScreenMan Tutorial for Developers Manual," particularly Lessons 1-2 (DISPLAY blocks) and 1-7 (EDIT blocks) for more information. This manual is available both in Adobe Acrobat PDF and HTML formats on the VA FileMan Home Page.
(Required) This property defines the location of the block. The format of a coordinate is: Row,Column.
A Block Coordinate is defined relative to the page on which the block is defined. A Block Coordinate of "1,1", for example, corresponds to the top left corner of the page. If a page is moved to a new position--that is, if it is given a new coordinate--all blocks on the page move with it.
This property is used if the fields displayed in this block are reached through a relational jump from the primary file of the form. The Pointer Link is a relational expression that describes this jump. See the "Relational Navigation" section in the "VA FileMan Advanced User Manual" for more information.
Pre Action and Post Action
The Pre Action property is M code that is executed whenever the user reaches this block. The Post Action property is M code that is executed whenever the user navigates away from this block. Since these two properties are stored in the Form file, they apply to the block only as it is used on this form.
Replication, Index, Initial Position, Disallow LAYGO, Field for Selection
These properties pertain only to repeating blocks. See the "Displaying Multiples in Repeating Blocks" section for more information about these properties.
Block Properties Stored in the BLOCK File
Since these properties are stored in the BLOCK file, they are part of the definition of the block itself. These properties apply to the block wherever it is used.
(Required) This is the .01 field of the BLOCK file (#.404). Block Names should be namespaced.
This is the data dictionary number of the file or subfile that contains the fields that are placed on this block. A block can contain fields from only one file or subfile.
If you set this property to "YES," navigation within the block is disabled. When navigation is disabled, users cannot ^-jump to other fields, they cannot ^-jump to the Command Line, and the <ARROW UP>, <ARROW DOWN>, <Tab>, and <PF4> keys traverse the fields in the same order when pressing the Enter/Return key - that is, in the order established by the Field Order property of the fields. The <PF1> S, <PF1> E, <PF1> Q, and <PF1> C key sequences cannot be used if this property is set to YES.
If you set this property to OUTOK, navigation is disabled, but the user can ^-jump to the Command Line and use <PF1> S, <PF1> E, <PF1> Q, and <PF1> C.
Pre Action and Post Action
The Pre Action property is M code that is executed whenever the user reaches this block. The Post Action property is M code that is executed whenever the user navigates away from this block. Since these two properties are stored in the BLOCK file, they apply to the block as it is used on any page of any form.
Reviewed/Updated: March 4, 2007