x Want to participate? Join the group to interact
  • Replies 3 replies
  • Subscribers 134 subscribers
  • Views 2194 views
  • Users 0 members are here
Browse Forums
Announcements
268
topics
260
replies
Databases and Operating Systems
757
topics
2k
replies
Financials Suite
1k
topics
3k
replies
General Discussion
2k
topics
10k
replies
Operational Suite
851
topics
2k
replies
Reporting and Analytics
1k
topics
3k
replies
Reports, Macros, and Customizations
876
topics
3k
replies
Sage CRM for Sage 300
182
topics
410
replies
Jim Love

WARNING on 64-bit Excel with version 2022

Posted By

We recently upgraded a client using AP and GL only to version 2022.  Everything was fine.  Then they added a new Windows 10 workstation with 64-bit Excel.  (All previously existing workstations are running 32-bit Office.)  They ran an FR Balance Sheet on the new workstation, and it was out of balance.  They ran the same BS on a different workstation, and everything was there, balanced.  User login to Accpac made no difference.  I logged in remotely to verify - same FR form file run with the same parameters for the same period returned a statement with missing data, resulting in an out of balance statement.  We uninstalled Office and re-installed it as 32-bit.  Issue resolved.

  • Hi Jim, 

    Thanks for sharing these details. Forwarded them onto our Sage 300 ERP support team who wasn't able to replicated the issue. They had the same balance sheet results in both the 32 vs 64 bit versions of Excel. If you come across this again, the team would be happy to open a support ticket to look into this further.

    Warm Regards, 
    Erzsi

  • I have experienced the same issue with excel 64bit, when running balance sheet in FR designer on 64bit excel, report balanced, running balance sheet from Print Financial statements icon, it did not balance, so is a problem with the print icon process.

    same report using 32bit worked.

  • I believe the problem is that the Accounts in question are not associated with an Account Group Code.  

    When running via Statement Designer, it runs the following Select Statement pertaining to Account Group Code

     AND (ACCTGRPCOD <= "ZZZZZZZZZZZZ")

    Whereas when run from Print Financial Statements it runs this:

    AND (ACCTGRPCOD >= "00")

    So if the Account Group Code is unassigned then it is a Blank record.. the first statement will return the account, whereas the second will omit it.. 

    Workaround is to just associate the Account with an Account Group.

    Issue has been reported to Development.. 

*Community Hub is the new name for Sage City