Home → General Questions →

Qualcomm CPU

• Edit

Peter Puttagio

12 Feb, 2025 04:23 PM

I have a new PC - Microsoft Pro 11 - uses a Qualcomm Snapdragon x12 cpu - should i download the intel update or the ARM update for Moneydance?

1. Support Staff 1 Posted by Jenny on 12 Feb, 2025 05:24 PM

   

   Hi Peter,

   To check which processor your system uses, open your computer's Control Panel and select System and Security > System. Your computer's CPU model is displayed to the right of "Processor" under the System heading.

   --
   Jenny, Infinite Kind Support

   • Edit

2. 2 Posted by Peter Puttagio on 12 Feb, 2025 06:00 PM

   

   Snapdragon(R) X 12-core X1E80100 @ 3.40 GHz 3.42 GHz

   • Edit

3. Support Staff 3 Posted by Jenny on 12 Feb, 2025 06:03 PM

   

   Hi Peter,

   I believe Snapdragon processors are based on ARM architecture, not Intel.

   --
   Jenny, Infinite Kind Support

   • Edit

4. 4 Posted by Peter Puttagio on 13 Feb, 2025 07:13 PM

   

   I upgraded to the ARM version 2024.3(5219) and now the Net Worth on my Summary screen is way off - when I run my Networth Report it is correct - how do I control what accounts are being picked up by the Summary screen Networth -- I am assuming it is picking up some old accounts that I previously had active.

   • Edit

5. Support Staff 5 Posted by Jenny on 13 Feb, 2025 07:15 PM

   

   Hi Peter,

   In the latest version of Moneydance, a change has been made regarding net worth. Your net worth now includes inactive accounts (that have a balance). Previously, all inactive accounts were automatically excluded.

   To fix this, open Moneydance and select Tools > Accounts. All accounts in your data file will be listed here, with the inactive account names greyed out. Double-click on each of your inactive accounts to view the account settings. Then, disable the option 'Include in Net Worth' at the very bottom of the window.

   --
   Jenny, Infinite Kind Support

   • Edit

6. 6 Posted by Peter Puttagio on 13 Feb, 2025 07:46 PM

   

   Thanks for the quick response, that appears to have fixed the problem. Thanks

   • Edit