Old reconciled transactions mysteriously duplicating

In Quicken Deluxe Personal 2006 I have had two recent instances of old, reconciled transactions showing up duplicated in the register. The first was noticed when doing a reconcile a couple months ago when there was a discrepancy in the starting balance, by the amount of a fixed monthly payment. Turned out the May 2010 payment was suddenly there twice. (I don't do any online downloads). It obviously had not been there a month before when I was doing a reconcile. Just now I found a duplicated reconciled check from January of this year. I have deleted both. When I ran a validate, it gave no message of any problem. Any idea why this is happening? Or suggestions? The file is around 22mb and has transactions going back around 12 years. It was originally started in Q98.

TIA Jim

Reply to
kapjim
Loading thread data ...

snipped-for-privacy@example.com wrote in news:rgnc171o2t0f661e3rnrgs5i125kv903ng@

4ax.com:

You are running an old version of Q. Some years ago I had problems with data corruption of some kind as well, maybe it was around that version's time. My way around it then was to make at quarterly intervals a new database, by telling Q to copy the data to a new dataset. It seemed to me that Q wasn't too good at cleaning up after itself, and that led to corruption. Remember, every time you edit a transaction, you in effect create a new datapoint (database record) and simultaneously you tell Q to mark the old record as superfluous. The record remains in the database, but now marked as "to be disregarded". Only database cleanup can remove those records, which is most easily done by copying to a new database/set of Q-files.

I suggest to get a new version of Q soon, either Q12 when it comes out, or a cheap copy of Q11 when Q12 has superseded that.

HTH

Reply to
Han

Han wrote: :: snipped-for-privacy@example.com wrote in news:rgnc171o2t0f661e3rnrgs5i125kv903ng@ :: 4ax.com: :: ::: In Quicken Deluxe Personal 2006 I have had two recent instances of ::: old, reconciled transactions showing up duplicated in the register. ::: The first was noticed when doing a reconcile a couple months ago ::: when there was a discrepancy in the starting balance, by the amount ::: of a fixed monthly payment. Turned out the May 2010 payment was ::: suddenly there twice. (I don't do any online downloads). It ::: obviously had not been there a month before when I was doing a ::: reconcile. Just now I found a duplicated reconciled check from ::: January of this year. I have deleted both. When I ran a validate, ::: it gave no message of any problem. Any idea why this is happening? ::: Or suggestions? The file is around 22mb and has transactions going ::: back around 12 years. It was originally started in Q98. ::: ::: TIA ::: Jim :: :: You are running an old version of Q. Some years ago I had problems :: with data corruption of some kind as well, maybe it was around that :: version's time. My way around it then was to make at quarterly :: intervals a new database, by telling Q to copy the data to a new :: dataset. It seemed to me that Q wasn't too good at cleaning up :: after itself, and that led to corruption. Remember, every time you :: edit a transaction, you in effect create a new datapoint (database :: record) and simultaneously you tell Q to mark the old record as :: superfluous. The record remains in the database, but now marked as :: "to be disregarded". Only database cleanup can remove those :: records, which is most easily done by copying to a new database/set :: of Q-files. :: :: I suggest to get a new version of Q soon, either Q12 when it comes :: out, or a cheap copy of Q11 when Q12 has superseded that. :: :: HTH :: -- :: Best regards :: Han :: email address is invalid

And to be clear here, performing a 'copy' is with the built-in Q file operations, not a Windows copy from Windows Explorer which will do nothing in terms of file cleanup. Easy to forget this fact now that everything is in one .qdf file as of whatever the recent release was that consolidated all of this (2009?).

Reply to
Andrew

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.