There are a few fundamental rules of the macro language.
It consists of ‘Lines’, separated by Carriage Returns, each of which can contain just one ‘Command’.
Blank Lines are allowed, as are spaces in front of Commands.
Commands can be one or more words long, and there must always be a single space between the words of Commands.
Many Commands require one or more ‘Parameters’, which are contained within round brackets and separated from each other by semi-colons. Textual Parameters should be surrounded by double quotation marks, though these are in many cases optional. Numeric Parameters should not be surrounded by quotes. There is normally one space between a Command and the opening bracket of the Parameters, but this can be omitted or more spaces inserted. Some Commands possess optional parameters. If you are not using an optional parameter, you should still use the correct number of semi-colons, leaving a blank between them where you have omitted a parameter.
Lines containing typing errors will generally not cause errors, but will simply be ignored.
Two types of variable can be used in macros.
Global variables will retain their value within the process in which they are being used. It is recommended that you distinguish global variables in your macros by prefixing them with the letter “m” (for example, mVar). This will also eliminate any possible confusion caused by duplicating the names of the global variables used by Enterprise 6 itself (in Enterprise 6, global variables begin with the letter “v”).
Interprocess variables retain their value at all times and must be preceded by <> (for example, <>Var) on the Macintosh, or the 2/3 character on Windows machines. You can create your own interprocess variables and use those already in Enterprise 6, either testing or altering their current value. Note that interprocess variables may be used by Enterprise 6 in many areas of the application, so altering the value of an existing one may cause unexpected results and must be avoided.