REBUILDING THE GL INDEX IN FRX

When you create row formats in FRx, you need to specify which General Ledger Accounts will be used in the reports.  When you later add accounts to the chart in MAS90 or MAS200, you need to make sure these changes are reflected in the necessary row formats.  

You may find that after adding the accounts to the chart and to the FRx row format, they do not appear on the report, or FRx generates an error stating it cannot find the accounts.  In this case, you will need to rebuild the GL index in FRx.  This procedure forces FRx to re-read the MAS90/200 GL1 file to verify all the accounts. 

To automatically rebuild the index, go to the Admin menu in FRx, then Build Local GL Index.   FRx will generate a message that this may take time.  Click OK.  Once this has completed, generate the report again to see if the account has been included.  If not, you will need to manually rebuild the index.  

To manually rebuild the GL Index, close down FRx.   In Windows Explorer, find the frxwin\sysdata folder.  This may be either on a network drive or your local drive depending on how FRx was installed.  Once you are in the sysdata folder, look for files with a .g32 extension in FRx version 5 or 6, or a .glx extension in earlier versions.   These files are the GL Index files.  You will notice your MAS90/200 company code along with a consonant and a number.  An example of the index file for company ABC would be abca10.g32 or abca10.glx.  Find the company code where you are having the problem and right click on the file.   Rename the file extension from .g32 or .glx  to .old or .bad.  Be sure you do not delete the file in case there is a problem.  

Now exit Windows Explorer and restart FRx.   Once you log into FRx, you will notice a message in the left corner that it is rebuilding the GL index.   FRx now has accessed the latest version of your chart of accounts.

*NOTE: These instructions presume that you have a working knowledge of MAS90, MAS200 and FRx as well as Windows Explorer. Accuvar assumes no responsibility for any data loss or downtime caused by performing the above tip.