Scary QD2010 error

OK, this is getting old. This error just happened again today, this afternoon.

Immediately after a OSU I noticed that yet another seldom-used credit card had what looked to be an incorrect balance. Since I'm getting to be an old hand with this problem I just scrolled up to the top of the register and, once again, the "Opening Balance" entry - an entry that I've *always* established as a $0 entry, had a charge of $40.08 that wasn't there this morning. (I confirmed this by opening the last Quicken regular backup, which just happened to be this morning, and verifying that the "Opening Balance" entry was $0.)

This error was introduced silently via this afternoon's OSU. When I did the OSU there was one transaction downloaded, a payment on the account in the amount of $22.66, which was correct and I accepted it. Unlike the two previous errors documented above, I couldn't see any entry in the register that OSU might have "keyed" on to come up with the $40.08. All entries in the register had either a 'c' or 'R' in the Clr column, there were no single entries of $40.08 anywhere in the register and the "recent activity" in the account (previous activity was back in Feb, 2010) were 2 transactions amounting to $22.66 and the payment.

I guess at the point I get to talk to India.

Tom Young

Tom,

Just a thought.

It appears that the entry involved is always the Opening Balance entry which is $0.00. Why not delete it and see if that solves the problem.

As a general practice, I always delete the $0.00 Opening Balance entries that are automatically generated when setting up a new account. I see no reason to have a $0.00 balance entry in the register. Of course, I don't delete them if they have an actual balance.

You could create a new Windows folder; create and open a New Quicken file in that folder (making that new folder; the "current" folder); restore any backup that has the $0 opening balance transaction; delete the opening balance transaction; and do another download to that restored file.

You could then delete the entire new folder when you were through testing.

I'm not sure what you want to "prove". But my thought is that, if you want to increase the chances that Intuit can recognize, and fix, a problem ... it could be benefical to gather, and publish, more evidence.

You normally explain problems very clearly - that's something that software developers appreciate (if not, requre). You could provide your evidence at: