Reports - Microsoft Office Documents

SOLVED

Sage 50 Pro Canadian Edition

I'm trying to print a Chart of Accounts with GIFI codes.  Since the Code field is not available to the Chart of Accounts report, I went to Reports > Microsoft Office Documents... and found in the resulting list a report entitled "Chart of Accounts with GIFI Codes", Type "Excel".  When I attempt to open the report, Excel opens a spreadsheet populated with data (but not my data) and I get a dialog box asking if I want to refresh the report.  If I say no, the Excel file remains open but is filled with sample data. If I say yes, Sage displays another dialog asking me to choose a database for generating the report.

What database is it looking for?  If I select a *.saj file, Sage produces another dialog asking for authorization and a username and password.  Since I'm on a single-user installation, I have no clue what Sage is asking for.

Any ideas?

  • 0
    verified answer
    In answer to your first question, Reports, Lists, Accounts allows you to put the GIFI code column on the report.

    For the database you want in the MS Office Documents Excel report, you should have a look at File, Properties before you run Reports, MS Office Documents so you will know which company file (*.sai) to run the Excel spreadsheet on. If you don't log into Sage 50 with a user name and password, then use sysadmin with no password (see the bottom right-hand corner of the Home screen for your Username).
  • 0 in reply to Richard S. Ridings
    #1. So it does! Thank you for pointing out that the Accounts report is what I needed. This will do.

    #2. Ok, I have the file correctly identified, but sysadmin (the name in the corner) w/o password doesn't work. I'm normally quite strict with passwords and would have recorded it if I needed to create one. I honestly don't recall. Any further steps I can take?
  • 0 in reply to D Masters
    #2, probably not. If you don't use a password, the programming in Excel is not supposed to ask you for one. I've been told by a few people that the version of Excel being used can cause the programming not to work properly. I've made some edits once to the programming to make it work but I can't guarantee that programming change I made would work 100% of the time. I just don't remember the full reason right now because it was found a couple of years ago and I haven't dealt with it since. Mine works with Sage 50 2016 but I am using Excel 2007.
  • 0 in reply to Richard S. Ridings
    Understood, and thanks for the help. Because I have a work-around, I won't pursue this but I know to start looking at Excel 2010.