MIC defines a necessary extension to the standard form tag. Each form that will contain MICinputs, MIChiddens MICdisplays, or that part of a page that is in a chain of pages for which the coder wishes to ensure data propagation, must declare its fieldspace name within the form tag.
The name must be defined somewhere within the files which MIC is compiling with a MICfieldspace tag. The fieldspace must be defined in a .fs file. For maintainability and style (though not mandatory), only one fieldspace should be defined per file. This does not mean that one cannot have non-MIC forms, however. It is possible to have such forms and access their variables while within MICPerl tags, as one would in standard CGI scripting.4.5 See 3.2.2 for stylistic notes on when to employ each of the differing forms.
The value of the errorpage attribute is the name of a MIC-HTML page in the pile to go to if there is an error encountered during the verification process. This will override the default value supplied in the fieldspace definition for this form only.
Note that it is at the form tag (if a MICfieldspace is specified) that the fieldspace object will be instantiated. Refer to 3.1 for how this will affect the execution of the page.