'Delete' transaction ships to unrelated transaction

Using QD 2017. Does anyone else have this problem where I have a transaction focused in the register, then when using the EDIT->TRANSACTION->DELETE function, focus 'skips' up a few lines to an unrelated transaction asking to confirm the deletion?

Reply to
Andrew
Loading thread data ...

Yes I've been having the same issue even still after the most recent update It messes things up when it decides to jump up a few transactions to delete an unrelated transaction until I realized it was happening. I've discovered if I use the delete rather than transaction, delete it will not jump and deletes the current transaction, where one had highlighted it correctly.

BEL

Reply to
Barbara

"Andrew" wrote

Using QD 2017. Does anyone else have this problem where I have a transaction focused in the register, then when using the EDIT->TRANSACTION->DELETE function, focus 'skips' up a few lines to an unrelated transaction asking to confirm the deletion?

-------------------------------------------------------------

I don't see it. Q2017 R5 or R6.

Do you get the same result when you create a New (test) Quicken file with a few transactions in a test account?

Does this Quicken Community discussion pertain to your problem?

formatting link

Reply to
John Pollard

Barbara - yes, you're right! Thanks for this work around.

John - I did set up a new Q file with six transactions, and the FILE method worked OK on all; they were composed of a variety of reconciliation types (U/C/R) just to mix it up a bit.

Maybe I'll try a validate or supervalidate on a copy of my live file just to see if that works, or maybe make a copy of the live file in case there's some internal transaction linkage issues that might be in play here.

Knowing you, I trust this is a new issue for you and you didn't see it in the myriad of other fora that I know you also track.

Reply to
Andrew

"Andrew"

John - I did set up a new Q file with six transactions, and the FILE method worked OK on all; they were composed of a variety of reconciliation types (U/C/R) just to mix it up a bit.

Maybe I'll try a validate or supervalidate on a copy of my live file just to see if that works, or maybe make a copy of the live file in case there's some internal transaction linkage issues that might be in play here.

Knowing you, I trust this is a new issue for you and you didn't see it in the myriad of other fora that I know you also track.

---------------------------------------------------------------------

I only use Q2017 for testing at this point, but may be switching to it soon.

I had not heard of your problem before this morning; so after reading your post here, I tested in my Q2017 test file and could not reproduce the problem.

But the Quicken Community discussion I posted the link to sounds very similar to what you report, and it appears that it is a known problem (just not known to me).

Reply to
John Pollard

"Andrew" wrote

John - I did set up a new Q file with six transactions, and the FILE method worked OK on all; they were composed of a variety of reconciliation types (U/C/R) just to mix it up a bit.

-------------------------------------------------------------

Ok, Andrew; I think I can explain why I did not see the problem and why your test also did not exhibit the problem.

Basically: our test account registers probably did not contain enough transactions.

I believe the problem is the one known as the "click through" problem. Some Quicken menus are passing clicks through to whatever is behind the place in the menu where you are clicking. So you're getting two clicks for the price of one.

For example: If the "Delete" choice in the Transaction menu is sitting directly above a different transaction in the register than the one you want to delete, that different register transaction will also get clicked on when you click "Delete".

When we tested, there probably was no other register transaction under the menu "Delete" choice, because we only had a few transactions in the register.

The problem could also cause you to initiate one of the tasks on your Quicken Toolbar, if that task's icon happened to be under the menu choice you selected.

That also explains why using the CTRL+d key sequence to delete a transaction does not cause the problem ... no click was involved.

Reply to
John Pollard

John, again thanks for the post. I am 'following' that forum (never heard of THAT one before 'satisfaction.com!?) until this is closed/resolved. Whoever posted (3 months ago) mentioned a fix soon. Time will tell.

Interesting problem, never heard of that before. (I chuckled with your comment "So you're getting two clicks for the price of one.")

Reply to
Andrew

If you're a hard-core main-menu user, here's a workaround.

At the start of every Quicken session, do Help > Enable Accessibility, which can be achieved via Alt-H, A if your menu won't cooperate.

The "accessible" menu doesn't suffer from "click through menu" bug. Unfortunately, the accessibility setting is not persistent across sessions.

We're also seeing a new, intermittent, main menu bug in '16 & '17 where the main menus close before the user has a chance to click on a menu item. The accessible menu also remedies this.

Reply to
Bob W.

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.