•These messages usually do not interrupt diary generation, unless you asked Q++Studio to interrupt diary generation after a certain number of errors.
•Once diary generation is completed, if there are any errors, a button will appear on the status dialog, list errors, which allow you to either view/print a list of generation errors, or view the location of the error in the output file.
Run-time messages are usually caused by a token that Q++Studio cannot evaluate, although some of the run-time messages are caused by design-time warnings that have been ignored (design-time messages are usually caused by a script line property).
Run-Time Messages are used to alert you to the same types of conditions and errors as design-time messages, but the difference is that the conditions that cause run-time messages could not be determined until diary generation began.
Q++Studio can perform a lot of checking at design-time and report errors. However token processing is an immensely rich and recursive process (holiday rules, recursive tokens, macros, Saras, …). Trying to perform all checks at design-time would require Q++Studio to be constantly performing background generation of the current script, and would slow it down to a grind.
Even if it was possible, some errors would never be caught since the data tables can be modified by other users, introducing recursive tokens into them, until the very moment a script is run. It would be an exercise in futility.
To avoid an overabundance of similar run-time messages, some run-time messages that are related to an issue which is not specific to a particular token (such as font or color problems), are only issued once, the first time that the conditions that cause that message are met.
See also: messages overview.
Topic 108051, last updated on 14-Oct-2023