HelpPages

Home | Developer | Frames | Screens | Transactions | Tiny Transactions

Tiny Transactions

    SCREENS - TINY MOVEMENT (settings)

    To setup a screen of tiny type movements, we wil set up two or, if we need a foot or summary of movement, three screens.
1. Display data header. This screen is configured in the same way as a maintenance screen with one limitation: The first field should be the first field in the table as it has to be the first field of lines screen (next screen). In most cases, one of the following fields is a date, and usually also be a cross-reference to a master file, such as an account number. If we want the cross-reference or call relational, we present additional information such as account name, we can add a field for this purpose. To activate this field we need a trigger (trigger) is activated by modifying the relational field (see triggers in advanced screen).
2. Screen lines. This screen will be the one wich accepts the different items associated with the main header (see Transaction tables in databases). The first field in this screen should be the same as in the first, or, whether a field of the main table. Furthermore, to avoid incorrect modifications by the user, must be a read-only field (NOEDIT$)
3. Summary screen. this is optional and has no special requirements, since it is only informative. If it requires some user input on this screen should be associated with an internal variable for further processing during data recording (FTCLC$ and  FITCLC$).
    To move from screen to screen, use the buttons at the top (<) for the front and (>) to the rear. For the summary, and thus conclude the input lines, you should use the cursor key down.
    A document already recorded, can be edited or deleted. To do this, in the first screen, we enter the document code to query, and press the "Enter" key.