Quicken for Mac v5.16 Released

caram

> @RickO said:
> Interesting. I would not have expected that.

@marcus, is there anything you can do to let us mere mortals have more/better editing options like some in the forum (you included)? It's pretty standard these days and it may be while until I get my 5-stars contributor stripe to access the </> button.

Also, enabling better quote options like you and some others have (indented grey background rather than >) would be neat.

Chris_QPW

caram said:

> @RickO said:
> Interesting. I would not have expected that.

@marcus, is there anything you can do to let us mere mortals have more/better editing options like some in the forum (you included)? It's pretty standard these days and it may be while until I get my 5-stars contributor stripe to access the </> button.

Also, enabling better quote options like you and some others have (indented grey background rather than >) would be neat.

From what one moderator said you need to get to 51 points to get the "full editor" with inline pictures and the HTML quoting and such.

You can see the number of points you have by looking at your profile.

caram

> @Chris_QPW said:
> From what one moderator said you need to get to 51 points to get the "full editor" with inline pictures and the HTML quoting and such.

[removed - off-topic]

Steven T Williams

Still can't print a simple Balance Sheet (Net Worth..) ON ONE PAGE for a past date that looks exactly like the sidebar with different numbers. Painful.

Jeff B

Just cloned my hard drive and used it to install and test Quicken 5.16 - hoping Quickfill is fixed. It's better, but I still have to go into an old transaction, open the Quickfill dialog, then create the new one to get the all the info automatically filled out. Basically more work to run 5.16 than it is to stay at 3.x, where everything fills out perfectly when I enter the payee of a new transaction.

There's no way to get Quickfill to automatically recognize and use the memo field from previous transactions - like it always had until version 4.x ? Seems silly to have to do all this work just to conform to the new version.

Deleting the clone, still sticking with version 3. Hate that I have to click "cancel" twice every time I launch Quicken, wish I could turn off the notification about the new version, afraid I'm misfire and accidentally update.

jacobs

@Jeff B I'm not sure I understand what problem you're having. In the current version, you can set a preference whether you want Memos automatically updated in QuickFill rules or not. Or you can override the preference on an individual transaction-by-transaction basiss to update the Memo field. And you can manually set individual QuickFill rules to have the Memo you want, and lock them to be unchanging. It's much more flexible than Quicken 2017.

Jeff B

@Jacobs I checked preferences to retain all fields in Quickfill, then entered a monthly check I write, but the memo field was blank. Category was there, but not memo. Only way to get the memo field to show the account number I needed there was to go to a previous transaction, check the quickfill section under 'transactions', then go back and create the new check. Appears to be a one time step I'll have to do for each different payee. Categories automatically enter, but Memos until I open a previous transaction and save it into Quickfill - or am I missing something? For me it seems like less work, less clicking, by sticking with the old version Quicken 5.13

jacobs

@“Jeff B” Yes, you will have to trigger Quicken to save the Memo field info for each Payee once to get over the start-up hump. They built the updated to not build Memo information into QuickFill rules because they believe the majority of users do not want Memos to be stored. So those of us who DO want the Memo stored need to spend awhile building up QuickFill rules. You can do this by editing a previous transaction as you described or you can manually edit/create QuickFill rules.

Yes, it’s a bit of a pain, but it’s a short-term annoyance until you get QuickFill rules built for your frequently-used Payees.

You can stay on the old version if you want, but you’re going to need to move forward at some point. Since I’d guess most current subscribers have already upgraded, I think it’s unlikely they will make changes to the code that updates your database to have QuickFill rules, so you’re going to face this issue whenever you do update.

Jeff B

OK, thanks for verifying what I thought was the case. I thought I might have been had a setting wrong or something. I'm sticking with the old version for now, will likely lower my "premium" subscription since I'll get no benefit from it.