Files > FORM

name
FORM
number
.403
location
^DIST(.403,
description
This file stores ScreenMan forms, which are composed of blocks. The form's attributes that describe how information is presented on the screen are contained in this file.
Fields
#NameLocationTypeDetailsIndexDescription
.01name(+)0;1FREE TEXTBEnter the name of the form, 3-30 characters in length. The form name must be unique and cannot be numeric or start with a punctuation character. It should also be namespaced.
1read access0;2FREE TEXTNon-programmers can enter only their own VA FileMan access code(s).
2write access0;3FREE TEXTNon-programmers can enter only their own VA FileMan access code(s).
3creator0;4NUMERICThis is the DUZ of the person who created the form. The ScreenMan options to create the form automatically put a value into this field.
4date created0;5DATE-TIMEThis is the date the form was created. The ScreenMan options to create the form automatically put a value into this field.
5date last used0;6DATE-TIMEThis is the date the form was last used. ScreenMan automatically puts a value into this field when the form is invoked.
6title0;7FREE TEXTCThe TITLE property can be used by the form designer to help identify a form. It is cross referenced and need not be unique. ScreenMan does not automatically display the TITLE to the user, but the form designer can choose to define a caption-only field that displays the title to the user.
7primary file(+)0;8FREE TEXTEnter a file number, greater than or equal to 2, which represents the data dictionary number of the primary file for this form.
8display only0;9BOOLEAN0:NO
1:YES
This is a flag that indicates none of the blocks on the form are edit blocks. This flag is set during form compilation.
9form only0;10BOOLEAN0:NO
1:YES
This is a flag that indicates none of the fields on the form are data dictionary fields. This flag is set during form compilation.
10compiled0;11BOOLEAN0:NO
1:YES
This is a flag that indicates that the form is compiled. This flag is set during form compilation.
11pre action11;E1,245FREE TEXTThis is MUMPS code that is executed when the form is first invoked, before any of the pages are loaded and displayed.
12post action12;E1,245FREE TEXTThis is MUMPS code that is executed before ScreenMan returns to the calling application.
14post save14;E1,245FREE TEXTThis is MUMPS code that is executed when the user saves changes. It is executed only if all data is valid, and after all data has been filed.
15description15;0WORD-PROCESSING
20data validation20;E1,245FREE TEXTThis is MUMPS code that is executed when the user attempts to save changes to the form. If the code sets DDSERROR, the user is unable to save changes. If the code sets DDSBR, the user is taken to the specified field. In addition to $$GET^DDSVAL, PUT^DDSVAL, and HLP^DDSUTL, you can use MSG^DDSUTL to print on a separate screen messages to the user about the validity of the data.
21record selection page21;1NUMERICEnter the page number of the page that is used for record selection. If you define a Record Selection Page, the user can select another entry in the file, and, if LAYGO is allowed, add another entry into the file without exiting the form. The Record Selection Page should be a pop-up page that contains one form-only field that performs a pointer-type read into the Primary File of the form. The Record Selection Page property should be set equal to the Page Number of the Record Selection Page. The user can open the Record Selection Page by pressing L. After the user selects a record and closes the Record Selection Page, the data for the selected record is displayed.
40page40;0MULTIPLE.4031

Not Referenced