Sage 300 - FR - Microsoft Compatibility checker?

SOLVED

Hello,

When I generate a Financial Statement in Sage 300 I now get a MS Excel Compatibility Checker warning.  When I generate numerous reports at once I now have to sit there and push 'okay' for the process to continue.  

This did not happen until last week.  I did not change my version of Excel or Sage.

Any suggestions on how I can stop this from happening?

thank you.

John

  • 0

    Uncheck the "Check Compatibility" box, or remove the links.

  • 0 in reply to Jay Converse Acumen

    I'm now getting this exact same 'Minor loss of fidelity' issue that has suddenly started popping up. No matter what I try, I can't seem to suppress it. Even unchecking the "Check compatibility..." box only applies to the current filesave - a nightmare when you have vba code saving multiple files, one after the other. And there's no way to break out of the vba to determine if there is truly a "link" as the notification implies. However, since the FR reporting has already generated the excel spreadsheet, I don't believe there should be any active links back to the original source.

    I think the solution is to somehow suppress the excel compatibility checker, but I'm unsure how to do it from Sage 300 VBA . Code such as 'Application.DisplayAlerts = False' doesn't seem to work.

    Chris

  • 0 in reply to Jay Converse Acumen

    I wanted to follow up on my post from yesterday. After some experimenting, I've determined that this is an issue with Microsoft Excel. In my case, it's Excel 2019. I fired up my old desktop running Win 10 & Excel 2007 and ran the same VBA unimpeded. It worked as expected without any compatibility warnings. I know this solution won't help everyone, but at least there's a way if you have an older desktop around. In the meantime, I'll still keep searching for a way to get things to work under Excel 2019 or later.

    Chris

  • +1 in reply to phscb
    verified answer

    I solved my compatibility issue.  I realized that the templates I was using to generate the FS were made 20 years ago.  Why I only started getting comp. warnings last week....who knows.  Anyway, I opened a new excel workbook, copied the code from the old templates, saved...boom fixed.