We covered basic macro information over the last two weeks. This week we've got some advanced features.

1) Move macros from version to version.

Sometimes recorded macros won't run after an upgrade or a service pack. Open the macro file (.mac) in notepad and remove the top line. It will look something like this: # DEXVERSION=DEX 8.00m076 2 2 and indicates the version the macro was recorded in. Since many GP updates add features, rather than changing features this usually works fine.

2) Split up macros.

This was covered in last weeks Weekly Review

3) Allow access to limited areas.

This was more important in past versions but if a user needs…

When building a macro, you can pause to allow for user input with the Insert Pause button. The problem is that the user has to know to go to Tools->Macro->Continue after they input their information. This extremely non-intuitive.

A better option is to build multiple macros. Let each macro stop before…

A macro is a function that allows the automation of certain events in a program. In Great Plains, macros can be used to take out some of the annoying parts. For example, when we transfer money, we always transfer it one way, from Money Market to operating. Everything is the same but the dollar amount. So, I build a macro to fill in everything but the amount. Now I just run the macro, add an amount and I'm done.

Building a macro in GP is easy but…