Table of Contents
Advertisement
ADOBE FRAMEMAKER 6.0
63
Using MIF Statements
Optional control programs allow you to tightly integrate the database and the FrameMaker product.
•
Some database publishing applications are controlled entirely from the database system or through
hypertext commands embedded in a FrameMaker document. More complicated applications may require
an external control program, such as a C program that issues queries and selects a FrameMaker document
template.
For an example of a database publishing application, see "Database publishing" on page 245.
Debugging MIF files
When a FrameMaker product reads a MIF file, it might detect errors such as unexpected character
sequences. In UNIX and Windows versions, a FrameMaker product displays messages in a console window.
In Macintosh and Windows versions, you must turn on Show File Translation Errors in the Preferences
dialog box to display messages in a window. If a FrameMaker product finds an error, it continues to process
the MIF file and reads as much of the document as possible.
When you are debugging MIF files, you should examine the error messages for clues. The MIF interpreter
reports line numbers for most errors. For a description of MIF error messages, see , "MIF Messages."
In some cases, the MIF interpreter reports an "invalid opcode" message for a statement. If the statement
seems correct to you, check the statements above it. A missing right angle bracket can cause the interpreter
to parse a statement incorrectly.
If the MIF interpreter brings up an empty document when it reads your file, it has stopped trying to
interpret your file and opened an empty custom document instead. Close the document and check your
MIF file for errors. Try adding a Verbose statement to your file to get more complete messages.
Advertisement
Table of Contents
