Skip to content

x Want to ask a question or reply? Click here to join the group.
  • State Verified Answer
  • Replies 5 replies
  • Subscribers 103 subscribers
  • Views 1329 views
  • Users 0 members are here
Browse Forums
Announcements
388
topics
261
replies
Databases and Operating Systems
606
topics
2k
replies
Financials Suite
738
topics
2k
replies
General Discussion
2k
topics
9k
replies
Operational Suite
459
topics
1k
replies
Reporting and Analytics
480
topics
1k
replies
Reports, Macros, Customizations and Developers
605
topics
2k
replies
Sage CRM for Sage 300
101
topics
268
replies

FR #value errors in Excel 64bit

Michael Seemann
Solved
Posted By

Hi Sage Community!

Old machine, Excel and Office 32 bit. Run report, no issues. New machine, MS 365 64 bit run exact same report and get #value errors in every calculated field. The formula is simple column D minus column C. Suppress zeros also fails. Report executes without errors, except the result is filled with #value errors. Again, same report works in 32 bit. Same result if I "design" or "run" the report.

Is this a subtle setting in Excel that didn't transfer over? A rogue add-in. I was under the impression that Excel 64 bit now works with Financial Reporter.

What am I missing here?

Michael

Details:

New machine: Window11, Office 365 64 bit, Sage 300 ERP 2024 PU3.

Old machine: Windows 10. Office 2016 32 bit, Sage 300 ERP 2024 PU3.

Parents
  • +1
    Verified Answer

    After reaching out to Sage Technical Support, it was deemed to be a bug, but also a bug that had no fix in 2024. It was suggested that we update to 2025 or later. Since we have a few 3rd party software modules, these upgrades are not always easy to do. We picked Spring Break and between finance and IT, we performed an update/upgrade to 2026 PU1. This issue/bug as resolved itself as a result of the update. If something else raises its head, I will reopen the case with Sage. As of right now, the issue is solved.

Reply
  • +1
    Verified Answer

    After reaching out to Sage Technical Support, it was deemed to be a bug, but also a bug that had no fix in 2024. It was suggested that we update to 2025 or later. Since we have a few 3rd party software modules, these upgrades are not always easy to do. We picked Spring Break and between finance and IT, we performed an update/upgrade to 2026 PU1. This issue/bug as resolved itself as a result of the update. If something else raises its head, I will reopen the case with Sage. As of right now, the issue is solved.

Children
No Data

*Community Hub is the new name for Sage City