Transaction date always reverts to current date
Comments
-
Always bugged me why they designed it this way. Hopefully they will change this soon.0
-
Yes, that is how it works in QM2007 too...much more convenient to keep the last entered date.
Have Questions? Help Guide for Quicken for Mac
FAQs: Quicken Mac • Quicken Windows • Quicken Mobile
Add your VOTE to Quicken for Mac Product Ideas
Object to Quicken's business model, using up 25% of your screen? Add your vote here:
Quicken should eliminate the LARGE Ad space when a subscription expires(Now Archived, even with over 350 votes!)
(Canadian user since '92, STILL using QM2007)0 -
I'm not sure what you're seeing. In QM18, if you enter a transaction with any date and you don't leave that register, the next transaction you enter will default to the date you last entered.Quicken Mac Subscription; Quicken Mac user since the early 90s0
-
That is true only if it is a "buy" transaction. If you do a dividend or Payment/Deposit transaction it always reverts to today's date.0
-
Hmmm. I'm not seeing that. After entering a Buy, Div or Payment/Deposit transaction in an investment register, then next transaction uses the last-used date, not today.H Franks said:That is true only if it is a "buy" transaction. If you do a dividend or Payment/Deposit transaction it always reverts to today's date.
Are you using QM18 v5.5.x?
I wonder if it has to do with column order. What is the order of your columns? My date column is the 2nd column with only Status to its left. Try dragging your Date column all the way to the left and see if the issue remains.Quicken Mac Subscription; Quicken Mac user since the early 90s0 -
Yes, that's my experience. It uses the last used date only in Buy transactions. I'm using quicken 5.5.3.Actually, if you enter any other transaction, it reverts to the last Buy transaction date afterwards.0
-
Same her. Date column is 2nd column.0
-
Ahah. Now that you explain it that way, I can also reproduce this.Hossam Shiaty said:Yes, that's my experience. It uses the last used date only in Buy transactions. I'm using quicken 5.5.3.Actually, if you enter any other transaction, it reverts to the last Buy transaction date afterwards.
Please report it using menu Help > Report a Problem. You won't get any feedback reporting it this way.
If you have time, you might also want to contact Quicken Support to report this directly (Help > Contact Support).Quicken Mac Subscription; Quicken Mac user since the early 90s0 -
So just to be clear, the root cause is the order of the columns that is affecting the date?Hossam Shiaty said:Yes, that's my experience. It uses the last used date only in Buy transactions. I'm using quicken 5.5.3.Actually, if you enter any other transaction, it reverts to the last Buy transaction date afterwards.
Have Questions? Help Guide for Quicken for Mac
FAQs: Quicken Mac • Quicken Windows • Quicken Mobile
Add your VOTE to Quicken for Mac Product Ideas
Object to Quicken's business model, using up 25% of your screen? Add your vote here:
Quicken should eliminate the LARGE Ad space when a subscription expires(Now Archived, even with over 350 votes!)
(Canadian user since '92, STILL using QM2007)0 -
No, it's not the column order. This was originally described as reverting to today's date. I wasn't seeing that.Hossam Shiaty said:Yes, that's my experience. It uses the last used date only in Buy transactions. I'm using quicken 5.5.3.Actually, if you enter any other transaction, it reverts to the last Buy transaction date afterwards.
Now that it's clear that the new transaction takes the date of the last BUY transaction, even if the last transaction entered was not a buy. The next transaction should take the date of the last transaction entered, whatever type it is.
Now that I understand the issue (which applies only to investment accounts), I can replicate it and the order of the columns doesn't matter.Quicken Mac Subscription; Quicken Mac user since the early 90s0 -
No, I didn’t say that. I just confirmed that my date column position matches yours . No idea whether that's the issue or not.0
-
I have the same problem too.0