If you actually read and comprehended what Quicken Had there been but a few posts in the Quicken Community, limited to simply explaining the problem (and possibly at least one user sending a complete Problem Report from Quicken), the solution would almost certainly have arrived just as quickly. Īnd you yourself answered the question you asked about 'what to do' in your original post here, when you posted in that Quicken Community discussion on August 6, 'I guess all we can do is wait.'. Your assumption that Quicken didn't care was totally unsupported by anything posted in the linked discussion (see above). In your original post in this discussion, you asked, 'I'mĪt a loss of what to do since neither party seems to care.'
The discussion you linked to is a good example of ignorant users pretending to know what they're talking about, as bogus grounds for making accusations and demands that they haven't the knowledge to make. No kudos are called for: Quicken Sarah had nothing to do with getting the problem fixed she's nothing but a messenger.Īnd it's extremely likely that the cause of the problem was with Apple.
