Classes and Sub-Classes -- Who Thought It Was Smart To Ditch These?

earshot

Hello Quicken Hive:

Has anyone come up with a script/macro/whatever to edit Quicken Mac 2007, etc. sub-classes in a way that will be meaningful in Quicken Mac 2016?

As many have written, the whole nature of accounting is categorical imperative, and we use sub-classes to track projects, ala the class "Jobs Active 2017" may have many sub-classes.

Ditching seems to be the thinking of someone who doesn't have to account for the $$$…

PPS

smayer97

So converting from QM2007 to "modern" QMac, classes and sub-classes would have all been converted to Tags. Unfortunately, there is no equivalent to sub-classes.

No real data should have been lost. Instead, the data is somewhat re-organized. Before, with sub-classes it was possible to be sure that sub-classes were only applicable to a class, so there was no risk of misusing a sub-class. Instead, you can think of tags as if classes and sub-classes have been flattened into one level.

The other trade off is that in QM2007 you could only assign one class or sub-class to a transaction. With tags, you can assign multiple tags to a given transaction, which can be a good thing. But as a result, you will have to be careful with double counting, depending on how you structure a report.

That all said, you should still be able to create the same project-based reports using categories vs tags instead of sub-classes.

There is a way to simulate sub-classes by naming your tags with a sub-class type structure by naming tags as "tag.subtag" or some such naming.

You can use the batch edit feature in Quicken by going into the All Transaction view. then filter according to the transactions you want to update. Select the ones you want to edit and select Get Info. This will bring up an edit window to batch update the selected transactions. One BIG caveat is that it does NOT update split transactions, only single line ones. So its usefulness is limited. The fallback is to update transactions manually...which could be very painful.

Meanwhile, you can add your VOTE to Improve Batch Editing to include changing Split transactions.

First, click on the underlined link above to go there, then click the little grey triangle under the VOTE count at the top of page 1 in the blue banner, so your vote will count for THIS feature and increase its visibility to the developers by seeking to have the features you need or desire end up in the latest version (it may take a moment for your vote to register).

Your VOTES matter!

volvogirl

I don't know about sub classes or Mac but in Windows Classes are now called Tags.

smayer97

So converting from QM2007 to "modern" QMac, classes and sub-classes would have all been converted to Tags. Unfortunately, there is no equivalent to sub-classes.

No real data should have been lost. Instead, the data is somewhat re-organized. Before, with sub-classes it was possible to be sure that sub-classes were only applicable to a class, so there was no risk of misusing a sub-class. Instead, you can think of tags as if classes and sub-classes have been flattened into one level.

The other trade off is that in QM2007 you could only assign one class or sub-class to a transaction. With tags, you can assign multiple tags to a given transaction, which can be a good thing. But as a result, you will have to be careful with double counting, depending on how you structure a report.

That all said, you should still be able to create the same project-based reports using categories vs tags instead of sub-classes.

There is a way to simulate sub-classes by naming your tags with a sub-class type structure by naming tags as "tag.subtag" or some such naming.

You can use the batch edit feature in Quicken by going into the All Transaction view. then filter according to the transactions you want to update. Select the ones you want to edit and select Get Info. This will bring up an edit window to batch update the selected transactions. One BIG caveat is that it does NOT update split transactions, only single line ones. So its usefulness is limited. The fallback is to update transactions manually...which could be very painful.

Meanwhile, you can add your VOTE to Improve Batch Editing to include changing Split transactions.

First, click on the underlined link above to go there, then click the little grey triangle under the VOTE count at the top of page 1 in the blue banner, so your vote will count for THIS feature and increase its visibility to the developers by seeking to have the features you need or desire end up in the latest version (it may take a moment for your vote to register).

Your VOTES matter!