Management Reporter is a great new financial statement reporting software package that has many advantages over FRx. First and foremost, it is SQL-based instead of being an Access database. That alone is worth its weight in gold. The ability to create reports via a built-in wizard and store reports in cohesive groups, along with a host of other features makes it a product many are anxious to implement.
Based upon recent installs of this exciting new product, we have some tips to make your experience with FRx to Management Reporter migration much easier.
Login: We’ve found that the Login for MR is done via Windows Authentication/Active Directory. However, once you’re in MR you need to connect to the databases via SQL authentication using your Great Plains login. This is how we found it works.
- The installation documentation tells you to set up a new domain user for Administration of Management Reporter. Since MR uses Windows Authentication for login, you must log into the workstation/server as this new user to log into MR as the Administrator and perform all the setups. This is well documented.
- Please note that user licenses are named users, not concurrent users. So a user cannot log in to Management Reporter unless logged into the workstation as one of the named MR users (user type of “Designer”, “Generator”, etc.) as set up within MR by the MR Administrator. Also, remember this: the MR Administrator user takes up one of your “Designer” licenses as Administrator. Be sure to note how many “Designer” licenses you own.
In addition to login features, here are a few more tips that might help with your installation of MR:
- If you don’t have Microsoft Office installed (specifically Microsoft Access) on the workstation/server on which you’re installing Management Reporter, you need to install a download or you’ll get an error saying “microsoft.ace.oledb.12.0 not registered”. You will also get this if the wrong version (64-bit versus 32-bit) is installed.
- You can only migrate one FRx specification set to one Management Reporter installation. If you have multiple specification sets, you must first combine them in FRx because any subsequent migrations from FRx to MR will overwrite existing reports. (This is documented in the migration manual.)
- You will need your .G32 files from FRx for the migration. It uses them to read account index information. So even though deleting .G32 files is usually the first step in anything having to do with FRx, don’t do it in this situation.
- If you have multiple company databases, migration can take some time. First, you need to set up all the companies in MR as there is no way to do this en masse. Then, once companies are all set up, migration of reports runs for quite a while.
Beth Hodge, Microsoft Business Management Solutions Professional
Intelligent Technologies, Inc.,