Michael Kaiser said: Are we becoming too acclimated to simply working around Quicken bugs? This is yet another example of core features not working as described.
Chris_QPW said: Michael Kaiser said: Are we becoming too acclimated to simply working around Quicken bugs? This is yet another example of core features not working as described. I have always believed that what sets an expert Quicken user apart from a "new user" is knowing what not to use in Quicken.
For Quicken in general, there is how they advertise it, and how it actually works (or doesn't work). Quicken has a long history of trying to provide features for the users but coming up short. And that ranges from nuisances to some cases, even corrupting data, and most of the time blaming the corruption on the users when most of the time it is Quicken or background processes that is doing the corrupting. Quicken is an example of "be careful what you ask for" where user's want to shoot for the moon but have to deal with the fact, they might end up at the bottom of the sea because either the Quicken developers didn't really understand the request, or because they are perfectly fine with a feature working 95% of the time. There is in fact nothing wrong with the concept of "close account", but because it is multiple steps across Quicken and also not properly implemented in my opinion it is more pain than a feature. I certainly get it. Quicken has "wizards" for a lot of things, and in general some of them work quite well. For an experienced user it isn't much of a deal. Remove reminders, zero account, remove online connections, set display options, ... But to the non-experts I can certainly see where they would like all of that to be handled for them. It certainly more "justified" than say voiding a check, which in Quicken Mac they complain about not having, when it is so simple to do, and not used very much. The trouble is that as the number operations go up, so do the possibilities of bugs and problems. I have no doubt that 95% of the time when you use close account that it will do all the operations including disconnecting the accounts from downloading correctly. It is the "edge cases" that Quicken fails at. That the "not properly implemented" part is a design decision that they made. They decided that you can't unclose and account. Let's face it, there isn't any real reason for that. In fact, Quicken Mac allows it. But more to the point Quicken is simply taking the same steps one can do manually. There isn't anything in the system that requires that the account stay "unconnected" or "hidden". This was their choice. And it has direct implications for this situation. If Quicken missed/error out on the step of deactivating the account during the closing of the account, it "assumes" that it is closed and as such has nothing on the Online Services tab to fix this situation manually.