Hi and thanks again for the replies.
I sorta feel that even though I am getting some great responses, I am not really getting an answer.
My thoughts are as follows:
- QB Desktop Pro 2020 supports classes out of the box
- In the Preferences, there is an ability to make classes "required" during data entry and to have the program "nag" you not to forget
- I "departed" using a spreadsheet solution of the past 25 years to use QB Desktop to not have to hack my way to solutions
- Since QB Desktop is built on top of relational database and has a built in reporting suite, I just expected things to "work out of the box"
Which really leads me to complete frustration when I ask the following and can't get a clear answer from the Intuit folks:
- since the data is all in a relational database, how hard is it to just have this work since (A) the quick report function (for any account) allows you to add the class category?
- if this does work on some versions of QB Desktop, why not all versions?
- if I don't want to export data and just use the reporting suite built in, what can I do to (A) find transactions that are missing classes, (B) do totals of accounts but only the part of an account that belong to a specific class and (C) why does the class function appear to be so software crippled AND is what is the point of including it and have the preference pane function to make it required if the "most basic" reports can not take advantage of it?
I do want to stress that I really appreciate all the people's time who have responded. I guess I am just shocked that this simple use case has gotten responses like (A) buy a more expensive version of the software and (B) use another tool to do more work (when the existing tool has a built in reporting suite). IMHO, this points to a problem and it would be great if this could be directed to the product and enhancement team at Intuit!
Best,
R
