How to prevent downloaded dupes?
in [Quicken]
|
Prev: Quicken 2009 loses keyboard focus on register entry
Next: Prices for European equities and mutual funds
From: news.astraweb.com on 4 Jan 2010 14:40 Constantly get duplicate downloaded transactions for BofA checking accounts and Amex credit card accounts. It's a pain. I emailed Quicken support and their response was of no use (how to remove dupes, rather than how to prevent them in the first place). Is there a solution for this issue. Quicken 2010 deluxe. thx
From: Robert Neville on 4 Jan 2010 16:13 "news.astraweb.com" <asasa(a)abc.com> wrote: >Constantly get duplicate downloaded transactions for BofA checking accounts >and Amex credit card accounts. I have the same problem with Amex. The original transaction shows up within 24-48 hours and download/match fine. Then a week or two later the same transactions show up again and have to manually be deleted from the download list.
From: John Pollard on 4 Jan 2010 20:44 Robert Neville wrote: > "news.astraweb.com" <asasa(a)abc.com> wrote: > >> Constantly get duplicate downloaded transactions for BofA checking >> accounts and Amex credit card accounts. > > I have the same problem with Amex. The original transaction shows up > within 24-48 hours and download/match fine. Then a week or two later > the same transactions show up again and have to manually be deleted > from the download list. If you want to get a handle on the guilty party; I suggest you plan to save two, or more, OFXlogs ... then compare the one that had the first download of the specific transaction; with the duplicate, later downloaded. You can see (and save) OFXlogs in Quicken > Help > Product and Customer Support > OFXlog. If you find that the second (the duplicate) downloaded transaction has a unique (never before downloaded) Financial Institution Transaction ID (<FITID>), you can lay the blame on your financial institution - they are the one's who assign the FITID. If you find the second (the duplicate) downloaded transaction has the same FITID as the originally downloaded transaction, you can probably lay the blame on Quicken ... though (I believe) the problem may actually also be caused by data corruption, and certainly by the loss of the .QEL file (from versions prior to Q2010) - problems over which, Quicken may have no control. For those inclined, Intuit has a piece of software that can tell you all the FITID's you currently have in your Quicken data. See: http://quicken.intuit.com/search/search-results.jsp?q=qellog -- John Pollard
From: XS11E on 6 Jan 2010 13:14
"John Pollard" <8plus7isf(a)gmail.com> wrote: > For those inclined, Intuit has a piece of software that can tell > you all the FITID's you currently have in your Quicken data. See: > > http://quicken.intuit.com/search/search-results.jsp?q=qellog To create a QELLOG.TXT file: 1.From the Quicken Online menu, choose Online Center. 2.Within the Online Center, press and hold the Ctrl key, and then click Update/Send. 3.Click the Create QEL LOG button, and then click OK. Followed by, "Quicken has encountered a problem and needs to close..." Quicken 2010, Vista Ultimate 64 bit. -- XS11E, Killing all posts from Google Groups The Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/ |