Developer’s Guide

Custom web publishing using CDML 8-13
6. Click an arrow or a subject title in the table of contents to view a
list of underlined topic titles. Then click an underlined title to view
the topic.
7. Click an arrow button to continue reading the topics in sequence.
Creating error messages
The FileMaker Pro Web Companion automatically generates an
error page for various errors that occur when web users access a
database. You can specify your own error pages to override the built-
in pages in the following ways:
1 Use the –error variable tag in a FileMaker Pro CGI request to
specify a single error page, which will be displayed for every type of
error that occurs.
1 Use the –error variable tag in the request to specify an error page
that contains [FMP-If] and [FMP-Else] replacement tags and
FileMaker Pro error codes, which determine certain conditions for
displaying an error message.
1 Include –errnum along with the –error tag in the request to specify
a range or single error code. You can use multiple –errnum tags to
specify discontinuous ranges, such as 500-510 and 900-978.
1 Include a specific error page with a filename that the Web
Companion recognizes when it’s located in a folder named “Error”
inside the Web folder.
The –error tag in a FileMaker Pro CGI request overrides both the
built-in error pages and the pages within the Error folder.
For any error page not included in the Error folder, the Web
Companion generates a built-in error page instead.
The Web Companion recognizes these error pages in the Error
folder:
NoResults.htm
ReqFieldMissing.htm
RepRelatedField.htm
UnexpectedError.htm
NotEnoughMemory.htm
DatabaseNotOpen.htm
LayoutNotFound.htm
DataEntryError.htm
DatabaseViolation.htm
FieldViolation.htm
SecurityDisabled.htm
FormatNotFound.htm
FileNotFound.htm
InvalidAddress.htm