Whenever I go to Manage VAT in QuickBooks I get the below error. I have had this issue in every version of QuickBooks and currently use QuickBooks Premier 2020 on Windows 10.
How do I fix this?
Can we ask you to follow this article to manually fix the Microsoft .NET Framework errors.
If you do find you then still have the same script populate when managing vat if you can do a clean and install, more information on how to do that can be found here.
Hi @EmmaM ,
I have done both the article to manually fix .net framework errors and a clean install, and neither of them worked. Also as stated this has happened now on quickbooks 2017, 2018 and 2020.
Thanks for keeping us updated, jack1289.
We'd really want to sort this out for you. Since you're still getting the same error after following the troubleshooting steps, please contact our Technical Support Team for QuickBooks Desktop.
They'll take a closer look at this and provide more options to resolve the issue. Here's how:
Let me know if you need anything else.
I found what I think the issue is.
I am using a 4K screen with a resolution of 3840 x 2160.
As the wording in quickbooks is quite small i tried to override the high DPI settings by right clicking the quickbooks 2020 desktop icon, going to properties and then to the compatibility tab.
After selecting Override High DPI scaling behavior” and setting the Scaling Behavior to “System (Enhanced), it firstly made the icons within Quickbooks very big, however the issue was then that the writing wasn't as clear, and i couldn't get much information fitting on my 17 inch laptop screen, as i can when the default DPI setting is set.
Before changing it back however i went into the Manage VAT menu, and the .net error saying "Value was either too large or too small for an Int32" does not appear. Also i was able to select between the radio buttons for view vat for last quarter or to date, which i have not been able to do before.
So it looks like the issue is that Quickbooks doesn't handle high resolutions screens well.
I have looked through some forums, and found that a lot of people have had this and the suggestion was to override the DPI scaling, but this really isn't workable and needs to be fixed properly.