A CHCS Input Template is allowed to include ";F" and ";N" Specifiers on individual multiple-valued Fields. A ";F" specifier "Forces" LAYGO; whatever entry the user makes to the multiple is considered to be "new", as though the user had typed it with quotation marks around it. Contrariwise, a ";N" specifier means "No" LAYGO is allowed for that multiple; the user can only choose from whatever Multiple values already exist. The Specifier syntax is case-insensitive, so that ";f" and ";n" are also allowed. DHCP FileMan Input Templates do not recognize this Specifier, and therefore do not support this functionality, which could be significant in the design of a particular application.
Portability Effect: Requires conversion. Any (scrolling-mode) Input Template ported from a CHCS environment to a DHCP environment needs to be examined for occurences of the ";F" and ";N" Specifiers. Converting such a Template to run in a DHCP environment exactly as it does in CHCS would probably entail special programming that makes separate ^DIE calls for each Multiple.
CHCS FileMan fixed a bug which still exists in DHCP FileMan Version 20. Suppose, within one Input Template, we want a user to descend into a certain Multiple Field more than once. For example, if ADMISSION were a Multiple Field in the PATIENT File, we might want the user to edit first the DISCHANGE DATE under one ADMISSION multiple, and then edit some "top-level" data about the PATIENT, and then edit the TYPE OF ADMISSION under a different ADMISSION multiple. DHCP FileMan would be confused by such an Input Template specification, and would "go down twice" to the same lower-level fields, DISCHARGE DATE and TYPE OF ADMISSION.
Portability Effect: Requires conversion. (Scrolling-mode) Input Templates built in a CHCS environment could specify such a "double descent" into a multiple. They would not be useable in DHCP FileMan because they have a different structure. Fortunately, this structure makes them easy to identify in an automated way: they are characterized by at least one non-integer subscript dependent from the Global node ^DIE(Template,"DR").
For example, a Template to do the kind of editing described in the previous paragraph would look something like:
^DIE(Template,0) = DOUBLE-DOWN^2940101...
^DIE(Template,"DR",1,2) = 401;.02;401;^2.01;
^DIE(Template,"DR",2,2.95) = 1;
^DIE(Template,"DR",2.01,2.95) = .02;
Note the "2.01" subscript just above. Converting such a Template to run in a DHCP environment exactly as it does in CHCS would probably entail separating the one Template into two, with a little special programming.
In the general FileMan lookup routine (^DIC), the user can enter a "?" when asked to select an Entry. If there is a large number of Entries from which to select (more than 18 or so), the user is asked something like
DO YOU WANT THE ENTIRE LIST? and at this point is allowed to enter an up-arrow(^) followed by a string of characters. This means, "show me the list, starting from this character string". In CHCS FileMan, the list of Entry names then displayed may include that input character string, if it is the exact name of an Entry. In DHCP FileMan, though, the display will begin with an Entry Name that follows the character string. For example, in DHCP, the following dialogue could occur:
Select FILE NAME: ?
DO YOU WANT THE ENTIRE FILE LIST? ^FORM
FUNCTION (47 Entries)
HOSPITAL (4 Entries)
.
.
In CHCS FileMan, the user would see, more appropriately,
Select FILE NAME: ?
DO YOU WANT THE ENTIRE FILE LIST? ^FORM
FORM (345 Entries)
FUNCTION (47 Entries)
HOSPITAL (4 Entries)
.
.
Portability Effect: Minor. This is perhaps an almost trivial difference in system behavior, but one which could require some user re-training if a CHCS user found himself in a DHCP FileMan "world".