HelpPages

Home | Developer | Frames | Screens | Maintenance | Maintenance Settings

Maintenance Settings

    SCREENS - MAINTENANCE (Settings)

    The basic configuration of a maintenance screen with AppDesigner is very simple, but must keep in mind some limitations of the program. First, the screen size is limited, but in AppDesigner it is unlimited, making it easy to make the mistake of designing a screen that subsequently can not be displayed completely. In the case of programming for a small display device, this question is essential.
    First, it is reasonable to put the text of the window, and a good strategy might be to put dots or dashes, where we want to be the data. But we must have at least two fields (the first will be the default key for searches, for example a code). Once this is done we can test the result in the program database.
    To set the fields, we must locate the cursor in the first position where we want to set the data field and then press the key "|" (ASCII 124) (AltGr 1). This allows us to access a screen where you indicate the number of the corresponding table, the column number, the data type and length.
    Data types are the same as those used to define the tables:

    A. Alphanumeric
    B. Alphanumeric Digits. (It behaves as alpha but only supports numeric digits.
    D. Only supports longitues Dates 6/8.
    L. Logical. 1 only supports lengths.
    N. Numeric integer
    1-9. Númeico with n decimal places.
    T. Time.

    You can also access this screen using the button "Field Attributes".
    Of course, in the application menu should be a button that links to this screen and to indicate to the database is a master maintenance.
    For example suppose we have designed our maintenance screen in a file called MYAPP, the display number 2. To make the link from the menu will indicate on the EXEC$ parameter corresponding to access this button:
    'MantMain MYAPP,2'

    In this type of display, there may be areas that do not correspond to the main table, for example data from another table, or data that comes from evaluting a expression. These fields should use the ASSIGN$ parameter, and will be read-only. By this parameter can also be assigned default values for a screen field.