Troubleshooting When Recording and Running Macros
While recording a macro an unwanted action was inadvertently recorded.
If you are using FlexPro Professional or FlexPro Developer Suite and want to undo an unwanted action in a macro, you can open the macro in the Visual Basic Editor and remove any unwanted steps. How to edit a macro. If you don't want to use the Visual Basic Editor, or it is not available to you, record the macro again without the unwanted action. |
Recording a macro occasionally produces an error message.
A macro you record may not run properly in every situation. If the macro cannot run, FlexPro displays an error message. Some macros depend on certain options or settings in FlexPro. For example, a macro that edits a selected object won't run properly if no object is selected. If a macro you've recorded produces an error message, note the error number. You can then search for "error messages" in Help and find information about the message you received. |
Cannot edit macros while project database is open.
If you are editing macros in a read-only database, you cannot save the changes you made. For a read-only database, FlexPro adds [Read-Only] to the file name in the title bar. |
Macro cannot be recorded if project database is open.
Recorded macros cannot be saved in a read-only database. For a read-only database, FlexPro adds [Read-Only] to the file name in the title bar. |
Cannot run macro while project database is open.
Changes resulting from running macros cannot be saved in a read-only database. For a read-only database, FlexPro adds [Read-Only] to the file name in the title bar. |