Copy/paste transactions deletes them?

Posted by Diver4242 on October 5, 2009, 8:32 pm

Please log in for more thread options

I'm using Quicken Windows Deluxe 2008. I had to add in an extra
paycheck for my wife since they got a bonus payment. So to make it
easy I went to a prior paycheck (they are scheduled in QW for every
two weeks) and did an Edit/Copy Transaction, then went down to the
bottom to an empty row, and then Edit Past Transaction and edited the
splits.

That went fine. I saved it, then there was some other transaction with
a new date in the empty line at the bottom, another paycheck for her,
and it wanted to know if I wanted to save that. i said No since the
one I copied/pasted was there. So then I realize that the original
transaction/paycheck is now gone, as if it did a CUT and paste.

I totally went through the whole thing again and made SURE I did copy
not cut, and it did this again. Now the whole thing is f'd up.

Is this a known bug or is there some way to fix this mess? I even saw
"undo delete" in the transaction menu and tried that and it didnt' put
this back.

If I can't trust Quicken to not delete my paychecks I can't use it.
What a mess.

Also the screen on Quicken keeps flickering, it's the only app that
does that, but occasionally it just randomly starts flickering about a
dozen times and it's pretty annoying when you are in the middle of
something.

Posted by John Pollard on October 6, 2009, 9:33 am

Please log in for more thread options

Diver4242 wrote:

> I'm using Quicken Windows Deluxe 2008. I had to add in an extra

> paycheck for my wife since they got a bonus payment. So to make it

> easy I went to a prior paycheck (they are scheduled in QW for every

> two weeks) and did an Edit/Copy Transaction, then went down to the

> bottom to an empty row, and then Edit Past Transaction and edited the

> splits.

> That went fine. I saved it, then there was some other transaction with

> a new date in the empty line at the bottom, another paycheck for her,

> and it wanted to know if I wanted to save that. i said No since the

> one I copied/pasted was there. So then I realize that the original

> transaction/paycheck is now gone, as if it did a CUT and paste.

> I totally went through the whole thing again and made SURE I did copy

> not cut, and it did this again. Now the whole thing is f'd up.

> Is this a known bug or is there some way to fix this mess? I even saw

> "undo delete" in the transaction menu and tried that and it didnt' put

> this back.

There's a known bug in Q2008 (and possibly earlier versions) that treats a
Copy/Paste in an investment account as a Cut/Paste. Fixed in Q2009.

I know of no problem relating to the copying/pasting of paychecks or any
other transactions in non-investment accounts.

Assuming we are not talking about an investment account ....

The part in your description about some other transaction - (apparently)
other than the newly pasted transaction - wanting to know if you wanted to
"save" it gives me pause; I don't see anything like that when I do a
copy/paste. That's the sort of message you get when you have made a
change to a transaction, then told Quicken to move the cursor to some
other transaction without pressing (or clicking) Enter.

If you did the paste, and did not modify the transaction date of the
pasted transaction, it would have the same date as the transaction you
copied, and as soon as you hit Enter, it would have moved to its
appropriate place in the register ... right next to the transaction you
"Copied". What happened from that point on, I can't quite figure, but
what you described (that second transaction needing attention) is not what
I see when I do a copy/paste. Maybe you did not actually "save" (Enter)
the pasted transaction, so when you tried to leave it, and told Quicken
not to Save it, you lost it.

Try the process again; only immediately after pasting the transaction,
press Enter (or click the Enter button). Then look in the register where
the original Copied transaction is, and note whether there is an exact
duplicate of that transaction.

--

John Pollard