Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Hi!
I've seen some troubleshooting, but I can't seem to solve my problem.
With QB2006 I had been using for years, I was able to export my data to Excel 2007 without much problems. Now with QB2020 Pro Desktop, I can't seem to obtain the 2 last columns to work right. I am using Microsoft 365 MSO 64 bits.
At first, I tried all the possible ways to convert the cells from Text to any kind of numbers, without success.
I've tried modifying the Regional settings for the computer, and many other things, but I am not getting ahead.
Now, it is important for me to keep the formatting as ### ###.##, thereby using a period between dollars and cents, and a space between hundreds and thousands.
At this point, I would love to be able to use the reporting directly to Excel without having to use the CVS detour...
A note: In the picture above, if for example I delete the space between the 1 and the 8 in the 1849.29 (first row) then the calculation is made until the -2 028.24. If I delete the space between the 2 and the 0, it will populate the Balance column until the next number. I did try to make a search and replace for that space, but it doesn't work.
Please .... help?
Thanks!
Hi Mouselette,
Glad to hear from you again. It's vital you get the support you need with this ASAP.
I appreciate you doing some troubleshooting on your end. At this point, I recommend contacting one of our agents for further troubleshooting. To find the contact details, please click this link here. One of our specialists will be happy to take a look at your account and assist.
Let me know if you have other questions. I'll be on standby.
Hello James!
Glad to be getting a reply!
I will certainly contact your contact. I am sure I'm not the only one trying to figure this out. W10 can be tricky with certain things...
I'll post back here if / when we figure this out.
Thanks!
Hey there, did you ever find out the solution because on my end I didn't
thanks
Hi,
It seems to be a problem with Windows, Microsoft Office and QB settings that don't "understand" each other.
In my case, I had an increase of workload, so I could not dedicate more time to solve the problem. It is irritating since before I migrated to the 2020 version, that feature worked flawlessly. Now, when I export to Excel, in the box "Send Report to Excel", I click on the "Advance" button, and deselect the Auto filtering option. When in Excel, I select the part with the amounts, and change the format to Numbers, and it seems to work for all amounts less than thousands. For the thousands amounts, I need to remove the spacing between the thousand and hundred for the amount to be taken into account in the calculations. So far, honestly, I only had the patience to export to Excel to do my cashflow. Other reports are longer, and I have no time to remove lines and lines of spaces ...
I don't remember how things are when using the .csv file export... last I used it, it seemed to work, but the formatting is lost...
Maybe someone else had better luck?
Thanks for getting back with further information, Mouselette. At this level, I'd suggest reaching out to Excel's support team for the best advice on how to move forward.
Here's the contact link to Microsoft: Microsoft Support.
Hi everyone!
It seems like the QB Tool Hub fixed a good part of what was not functioning - give it a try!
Thanks!
Glad to hear that the QB Tool Hub was of assistance @Mouselette! Great work troubleshooting. Drop by any time you have a QuickBooks-related question or concern. Take care.
Hi everyone!
It is finally figured out :-)
The problem is that QB works in English, and my W10 settings were for French.
The resulting reports are in English, and it's a real pain in the b**t since we function in French. But the numbers jive at least...
Have a great day!
You have clicked a link to a site outside of the QuickBooks or ProFile Communities. By clicking "Continue", you will leave the community and be taken to that site instead.