This run-time message is generated, and displayed in the macro interruption dialog, if during the evaluation of a macro token, the Assert function is called with its parameter bCondition false. The effect of the bAbortScript parameter is then:
•false: stops the current macro and records the message; diary generation continues.
•true: displays the interruption dialog below and aborts diary generation.
This is not an application error; it is an error generated because the person who wrote the macro decided that if certain conditions were not true, then an error should be generated.
the dialog which is displayed when bAbortScript is true
The second line contains the text of the sMessage parameter of the Assert function and usually describes what condition was not true. The third line gives you detailed information about the context in which the error was generated: the page number, the date of the token, the token being evaluated, and the origin of that token.
The origin of the token may be different than the token itself, if tokens are used recursively.
See also: LogMessage, Assert and RaiseError.
Topic 174275, last updated on 17-Oct-2026
