To recreate the Reports.dic, use these steps below:
Step 1: Export Modified Reports from the current Reports.dic file
- In Microsoft Dynamics GP, click Microsoft Dynamics GP, point to Tools, point to Customize, and then click Customization Maintenance.
- Select the forms or the reports that you want to export from the current dictionary files. Use the SHIFT key or the CTRL key to select more than one resource.
- Click Export.
- In the Please select a package file dialog box, select the location where you want to save the file, name the package file, and then click Save.
Note By default, the package file name is "PackageNumber.Package." The Number placeholder is a placeholder for the number that is incremented every time that an export is performed.
A progress bar shows the status of the export. If an error occurs during the export, the error is listed on the screen. Generally, reports that appear in the error list are not exported.
Step 2: Rename the existing Reports.dic file
- Make sure that all users exit Microsoft Dynamics GP.
- Using Windows Explorer, navigate to the GP code folder. Right-click on the Reports.dic file and rename it to Reports.bac. (The file or files may exist on the server or on the workstation. Review the local Dynamics.set file for the correct path.)
- Start Microsoft Dynamics GP and click on Tools under Microsoft Dynamics GP, point to Customize and click Report Writer. A new Reports.dic file will be automatically created.
Step 3: Import Modified Reports back into the new Reports.dic file
- In Microsoft Dynamics GP, click Microsoft Dynamics GP, point to Tools, point to Customize, and then click Customization Maintenance.
- Click Import.
- In the Import Package File dialog box, locate the package file that you created during the export process, and then click Open.
- In the Import Package File dialog box, click OK to start the import.
Notes
- The Import Package File dialog box lists all the resources that exist in the package file.
- A progress bar shows the status of the import. If an error occurs during the import, the error is listed on the screen. Generally, reports that appear in the error list are imported. However, users may be unable to print the reports.
(ALTERNATE STEP 3) Import the reports from within Report Writer
- Make sure that all users exit Microsoft Dynamics GP.
- Rename the Reports.dic file to Reports.bac. The Reports.dic file may be located on the server or on the workstation.
- Start Microsoft Dynamics GP.
- On the Tools menu, click Customize, and then click Report Writer. When Report Writer starts, a new Reports.dic file is created.
- Click Reports. The Modified Reports list is empty. If the Modified Reports list is not empty, you renamed the wrong Reports.dic file in the "Step 2: Rename the existing Reports.dic file" section. Find the appropriate Reports.dic file, and then start over in that section.
- In Report Writer, click Import.
- Click the ellipsis button (...) next to the Source Dictionary box. Locate the Reports.bac dictionary file that you named in step 2, and then click Open.
- In the Source Dictionary Reports list, select the modified reports that you want to import, and then click Insert. The reports are listed in the Reports to Import list.
- Click Import. When the Reports to Import list is empty, the modified reports have been imported into the new Reports.dic file.
Note If you created your own table relationships, the table relationships will be removed when you rename the Reports.dic file. After you import the reports, the table relationships that you created will be restored. If you created the relationship but did not link the relationship to a report, you must create the relationship again.
MORE INFORMATION
To
synchronize the forms and reports dictionaries to the GL account framework, refer to the steps in KB
857506.
To recreate the
forms.dic, refer to the steps in KB
951767.