"Cal Learner-- MVP" <via_newsgroup[at]please.tnx> wrote in message
news:eid80092lirmaq6e3gukm6gqu3c6goiad3[at]4ax.com...
- quote -

I located the transaction in the QIF that is causing the problem.
I made a one transaction QIF that fails.
!Type:Bank
D12/02/2003
NACH
Cc
PACH WITHDRAWAL--WEB / CITIBANK CRDT CD / ONLINE PMT
T-3134.57
^
There is a matching transaction already in the file for this item. The
matching transaction is the result of an online bill payment. Deleting the
matching transaction from the checking account register allows the QIF to
process properly.

One more point is that MS$ money program actually terminates while
displaying the screen that shows the downloaded statements that are ready
for processing, prior to clicking on the item to select it for processing.

I did do another repair and the file is OK according to repair process.

Definitely a MS$ program bug. Ahhhhh, One more reason to buy MS$2005!

Regards, Al

In microsoft.public.money, Al M wrote:

- quote -

Not that I can think of.

- quote -

I would do a binary search: delete half of the transactions at a
time.

Note that when you import the QIF as a statement from your bank,
Money looks for duplicate transactions. When you specify new or
recovered account, I don't think it does.

"Cal Learner-- MVP" <via_newsgroup[at]please.tnx> wrote in message
news:gr9800hh6efc9u9m6tglaujl1r2moop8gm[at]4ax.com...
- quote -

I took this step before posting the problem. I did it twice. Once before
running a recovery and once after.

- quote -

I'll do that when I have some time. Assuming that I find the "offending"
item is there anything in particular that I might look for in either the QIF
or the MS$ file? Examining the QIF file it appears "normal". At least
nothing stands out.

Al

In microsoft.public.money, Al M wrote:

- quote -

I would delete the download by right-clicking on the place in he
account list that says you have transactions to read. Then try
again. If it re-occurs, I would make a copy of my file and delete
transactions from my QIF file until I found the transaction that
appeared to be crashing. I understand there must not be an intrinsic
problem with the QIF file since it imports into other accounts fine.
Still, that's what I would do.

I download a QIF format statement for a checking account and import it into
MS$2004. All appears to go OK. When I go to the page to process the
downloaded statement MS$2004 abruptly aborts with "An error has been
encountered" message.

I have run standard file repair on the file prior to import and no problems
are found according to the log file. After the aborted attempt, doing a
file repair will indicate that a problem was found with the internet options
and was corrected. Attempting to use the repaired file I can not access the
transactions in the file that the import was for. I have to restore backup
file.

I have cleared the cache and reset maximum size to 50MB.

I can import the QIF that fails into a new account and all looks OK.

So far it is isolated to one account and one financial institution.

Other QIFs from other financial institutions import and process as expected.

Other than clicking on the "Send error report to MS" option are there any
know fixes or suggestions to this problem?

Al