Checklist for the "Error 9: Subscript out of Range" error message that may occur in Microsoft FRx


You may receive the following error message when launching Microsoft FRx for a company, or when generating a report:

Error 9 - Subscript out of Range.


Following are some steps that can be taken to resolve this isse:

1. Rename the *.G32 and any *.LDB files from the SysData folder with the FRx program closed.

2. Check that the Access box is checked for your functional currency in Microsoft Dynamics GP or in Microsoft Business Solutions - Great Plains (Setup - System - Multicurrency Access). If not, mark the box, then repeat Step 1.

3. Be sure to confirm the correct Default Accounting System under Company - Information and also under Admin - Processing Options is setup.

4. If the error occurs only when you print, create a very simple Row Format and Column Layout, use no Reporting Tree, and print the report to determine if you get the same error. If you do not get the error for this report, the Row Format and/or Column Layout being used in the report may be corrupt. To resolve, recreate the format.

5. Rename duplicate or outdated Bti.ini and Btrieve *.dll files that are on the server or local workstations. Repeat Step 1. and launch FRx.

6. Compact FRx databases when all other users have exited FRx (File - Compact FRx Database and complete both options).

7. Your Fiscal Period Setup data may be damaged. Follow these steps to recreate your fiscal periods.

a. Under Reports - Company - Setup - Fiscal Periods, print the report for all years. Take note of which years have the Historical Year field marked, as this is not included in the report.

b. IF SQL - With no one logged into the company, use ISQL to delete all rows from the company database.



c. Using the Fiscal Period Setup window, recreate the fiscal years by entering the Year, First and Last Day, Number of Periods, marking Historical Year when appropriate, and then clicking on the Calculate button. Use the printed reports to recreate and confirm the fiscal period information is correct.

d. Rename the *.G32 files from the SysData folder.

e. Launch FRx and print your report. If you still receive the error 9, continue with Step 8.

8. IF SQL - Run the following script in ISQL/Query Analyzer. If you receive results other than 0 row(s) affected, this was likely the problem.

select SGMTNUMB from GL40200 where SGMTNUMB not in (select SGMTNUMB from SY00300)

If your results were not ' 0 rows affected ', do the following:

a. Make a backup of your company database.

b. Delete the Segment Description Master table:


c. Run check links against the Account Master to recreate this table (File - Maintenance - Check Links).

d. Rename the *.G32 and any *.LDB files. Launch FRx. Note - If you still have the error verify that there are no extra segments in the GL40200 (select * from GL40200). If there are extra segments then delete them (delete GL40200 where SGMTNUMB = XX) (XX representing the extra account segment number).

9. IF SQL - In ISQL/Query Analyzer, run the following statement when Microsoft Dynamics GP is closed:


Then, run check links against the Account Master to recreate this table (File - Maintenance -Check Links).

10. If you are using a tree layout, verify that the company code in the Catalog of Reports is a company that is being used in column B - Company in the tree layout.

11. If you have the option 'Use Row Format(s) and Worksheet Links from Reporting Tree' selected in the Building Blocks tab of the Catalog of Reports and are using Row Linking in column I - Row Format in the tree layout, verify that there is a Row Link in each level, including the summary level, of the tree layout.

This article was TechKnowledge Document ID:6580

TechKnowledge Content

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.