Check reconciliation gone haywire

- A
- AFNMD
  
  Contact options for registered users
posted
17 years ago

Mon, Sep 25, 2006 1:24 PM

My checkbook reconciliations have begun to go haywire. Previous ones which were done correctly now show items as uncleared when they were cleared. Dates are now changed and starting and ending balances are different. I have tried going through them and repeating the reconciliation. Some have accepted the corrections and others have not.

My version of Quicken is 2003 and I have been getting messages that I needed to upgrade because Intuit was not supporting my "old" version. I can't help but feel that my problem is related to my "old", unsupported version.

Any thoughts?

Art

- C
- Christopher Range
  
  Contact options for registered users
Vote on answer
posted
17 years ago

Mon, Sep 25, 2006 6:20 PM

While it could be that, the quirks you mention, are eerily similar to, what has happened to my e-mail sometimes. Since I have a cable modem, I am able to constantly download my e-mail without any left on the ISP server. Anyway, Sometimes without warning, the date on any e-mail in my Inbox on my PC will, suddenly change to 01/01/1969. I was 5mths. from my 2nd birthday(May 16, 1967)!!!!

Simply put, upgrade. I have Quicken Deluxe 2005 because, I felt I needed to upgrade last year, so I did.

Christopher

- J
- John Pollard
  
  Contact options for registered users
Vote on answer
posted
17 years ago

Mon, Sep 25, 2006 6:34 PM

wrote

I don't believe your problem has anything to do with the age of your Quicken version. You may have data corruption, or you may have stumbled onto a bug, but there is no built in loss of function based on age (this is completely different from loss of online capability and Intuit support, known as sunsetting about which you have gotten messages).

There were some Quicken versions (Q2003 was one) that would get prior reconciliations messed up if the user modified the category (and possibly other fields: certainly the amount or cleared status) in a reconciled transaction. The only way to overcome that problem was to get into the "Resolve" dialog, delete every statement back to, and including, the oldest incorrect statement, and re-reconcile (I believe that the re-reconcile could be done by reconciling all previously reconciled transactions in one statement, making it somewhat less cumbersome).