I certainly did understand about possibly having the same FITID's and I had
checked sorting on the Downloaded ID column when Sherlock mentioned it. I
also checked the Quicken files and did a duplicate check on those. After a
lot of duplicate FITID checking and file modification, I then entered the
missing transactions manually after making the post and not finding anything
more on the Quicken site other than what I quoted.
And the idea of altering the downloaded file was also completed with no
effect as I mentioned in my original posting - you missed reading that.
Quicken in the past has had a bad habit of duplicating entries and causing a
lot of manual work to sort that out so I minimized the downloaded file to
only include the 2 entries when I re-imported it. No change, no errors.
While Sherlock was generous with his time to help assist with the details -
my question to the group was simply:
"Sent files and note to Quicken Help but wondering if anyone else is having
a problem with this update?
There are other problems being noted with this update if you do a search on
As for it being a Quicken problem or not remains to be seen. I'm certainly
no Quicken guru but I have worked with their software manager right after
the transition from the former company to test some beta patches for this
version (2017 Rental Property Manager). So yeah... Quicken has numerous
Your response still does not convince me that you understood what I said.
Searching for FITID's that match the ones in a newly downloaded file, is NOT
a conclusive way to determine that those FITID's have not been previously
downloaded. If you find duplicates, that will be conclusive; but if you do
not find duplicates, that does not prove there are no duplicate FITID's.
If the previously downloaded transactions that had FITID's equal to the
FITID's in the newly downloaded file, have been deleted from your Quicken
file, you will never see the duplicate FITID's in your Quicken file. Quicken
retains (and uses) the FITID's of deleted transactions, but nothing you do
will allow you to see them.
You say, "And the idea of altering the downloaded file was also completed
effect as I mentioned in my original posting - you missed reading that".
I read your posts carefully before my previous reply and I've read them
again now twice more, and I still do not see where you said you did what
Sherlock and I suggested in that regard. The modification that I suggested
(repeating Sherlock's suggestion) was "to alter the newly downloaded FITID's
...". I don't see where you said you did that. The idea was to guarantee
that the two problem downloaded transactions would be guaranteed to have a
unique FITID from any other transaction ever downloaded to that account in
Something which I don't recall you posting is what "Connection Method"
you're using. If you have a QFX file, that must have come from a Web Connect
download. Do you always download from the credit union using Web Connect, or
do you ever use another Connection Method, such as Express Web Connect? Or,
was any other Connection Method besides Web Connect ever involved in your
You may be able to get some indication about whether there is something
other than duplicate FITID's involved by creating a New (test) Quicken file,
and downloading/importing the problem account to that file. The results
won't necessarily be conclusive, but they might help, especially if the
"missing" transactions do not appear in the new test file.
As to Quicken having problems: that's hardly news. There is no such thing as
bug-free software, and Quicken has always had some bugs. That changes
nothing about the likelihood that your transactions are not appearing
because of a bug in the your release of Quicken. It may be true, but it's
not more likely just because your release, like every other release, has
The troubleshooting steps you've been asked to take, have at least a
reasonable chance of helping to identify the problem ... unlike wild guesses
(keeping in mind that correlation is not causation).