Macros have a very concise builder. There is no need for formatters, physical dimensions or other fancies; a macro is a doing object that is invisible to the user except in its expression, so the building really is as simple as it can get.
The macro ribbon offers tools to help design and debug macros. Debugging means stepping through the macro line by line to inspect how the macro executes its actions. The phrase debugging comes from the act of looking for code that produces undesirable effects, known as bugs.
The action list is a vertical list of actions the macro can perform. The actions are themselves called macros as well as the whole collection being called a macro (a little confusing so we’ll use action for individual lines and macro for the whole object).
Every action has a set of arguments against which the action is performed. The OpenForm action has a set of arguments including Form Name, View, Filter Name, Where Condition, Data Mode, Window Mode.
We hope that this post has helped you to understand the Macro designer.