Financial Reporter trouble?

Normal 0 false false false MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;}

I personally like Financial Reporter a lot.


It’s a compact and yet powerful tool. FR does not require additional software other than Sage Accpac and Microsoft Excel, also the reports are portable. And since it utilizes Excel as the macro base, all the handy Excel functions are the added bonuses.


My favorite thing about Financial Reporter is that the process of customizing a report is very thought-provoking.


All the benefits, of course, would only be beneficial if Financial Reporter starts properly, right? I have compiled a list of error messages that we get questioned about the most, as well as the Knowledge Base articles that could resolve them:


  1. Runtime error '429': ActiveX component can't create object – KB 21493
  2. Error on running STARTGL9200 or STARTGL9100 in xla macro – KB 24244
  3. Microsoft Visual Basic. Run-time error '91':Object Variable or Width block variable not set – KB 23601
  4. cmdStart: Error on running InstalledAddinAndXLStard – KB 26267


There are more that people might encounter, but generally speaking, FR errors could be resolved if the following conditions are met:


  1. Users have sufficient permissions on the operating system
  2. Excel installation has the proper components required by FR
  3. Security clearance is given to FR regarding macro or file permissions
  4. Accpac and Excel applications are up to date
  5. Last but not least, the shortcut to start Accpac should be pointing to the correct Runtime folder.


After resolving the initial errors, Financial Reporter will be much more interesting to work with. If you happen to run into any different error messages starting FR, we’d like to hear from you.