I am currently using a trial version of Microsoft Money
2004 Deluxe. The first week I used it, I was able to
download my bank transactions using the OFX file type and
it worked flawlessly reconciling with the bank ledger. I
now get a popup error meesage stating the import file is
corrupted, please contact your financial institution.
The date range of the download is no more than 30 days
worth.

The bank insist the problem is on my end.

What can I do to fix this? I do not want to use the QIF
file type because I have to reconcile the new
transactions as well as re-reconcile the transactions
from the previous import all over again.

Thanks, Dave

Re: corrupted import file by via_newsgroup

via_newsgroup
Tue Nov 11 11:15:52 CST 2003

In microsoft.public.money, davetroyer@microsoft.com wrote:

>I am currently using a trial version of Microsoft Money
>2004 Deluxe. The first week I used it, I was able to
>download my bank transactions using the OFX file type and
>it worked flawlessly reconciling with the bank ledger. I
>now get a popup error meesage stating the import file is
>corrupted, please contact your financial institution.
>The date range of the download is no more than 30 days
>worth.
>
>The bank insist the problem is on my end.
>
>What can I do to fix this? I do not want to use the QIF
>file type because I have to reconcile the new
>transactions as well as re-reconcile the transactions
>from the previous import all over again.

Troubleshooting and possibly fixing the file to work around the
problem are tricky. To get a copy of the OFX file saved, do Internet
Updates. When you get to the Connect button, hold down the
Ctrl+Shift keys as you click Connect. The file is saved as *RS.txt.
That file can be very confusing. Most people will not want to slug
thru it. One easy-to-find thing is that if, for example, "Tom &
Jerry's" was a payee, the ampersand should be replaced by these five
characters: '&'. If the ampersand is shown as only '&', that can
lead to the symptom. That is not probable, but is easiest to search
for.


Another possibility is that the current problem is transient. If
only one transaction is bogus and it is not going to be recurring,
you can delete that statement. Money will then request data from
after that statement the next time. If Money's request date is
honored by the bank's OFX server, you are on track. You would have
to enter the missing transactions manually or perhaps with the help
of the QIF download.

To delete a statement that has been read in but not processed, on
the Account List right-click on the "Transactions to read: n" spot.
"Delete statement" will be a choice.




Re: corrupted import file by davetroyer

davetroyer
Thu Nov 13 22:40:47 CST 2003


>-----Original Message-----
>In microsoft.public.money, davetroyer@microsoft.com wrote:
>
>>I am currently using a trial version of Microsoft Money
>>2004 Deluxe. The first week I used it, I was able to
>>download my bank transactions using the OFX file type
and
>>it worked flawlessly reconciling with the bank ledger.
I
>>now get a popup error meesage stating the import file is
>>corrupted, please contact your financial institution.
>>The date range of the download is no more than 30 days
>>worth.
>>
>>The bank insist the problem is on my end.
>>
>>What can I do to fix this? I do not want to use the QIF
>>file type because I have to reconcile the new
>>transactions as well as re-reconcile the transactions
>>from the previous import all over again.
>
>Troubleshooting and possibly fixing the file to work
around the
>problem are tricky. To get a copy of the OFX file saved,
do Internet
>Updates. When you get to the Connect button, hold down the
>Ctrl+Shift keys as you click Connect. The file is saved
as *RS.txt.
>That file can be very confusing. Most people will not
want to slug
>thru it. One easy-to-find thing is that if, for
example, "Tom &
>Jerry's" was a payee, the ampersand should be replaced by
these five
>characters: '&'. If the ampersand is shown as only '&',
that can
>lead to the symptom. That is not probable, but is easiest
to search
>for.
>
>
>Another possibility is that the current problem is
transient. If
>only one transaction is bogus and it is not going to be
recurring,
>you can delete that statement. Money will then request
data from
>after that statement the next time. If Money's request
date is
>honored by the bank's OFX server, you are on track. You
would have
>to enter the missing transactions manually or perhaps
with the help
>of the QIF download.
>
>To delete a statement that has been read in but not
processed, on
>the Account List right-click on the "Transactions to
read: n" spot.
>"Delete statement" will be a choice.
>
>
>
>.
>The & character is what's causing the corrupted
download. Why is this not a problem with MS Money 2001
and a problem with MS Money 2004? Anyway, I download the
OFX file from the bank's website and it automatically
imports it into MS Money provided MS Money is open. If I
have Money closed how do I locate this file to do a search
and replace of this ampersand character.

Really this is the bank's issue to replace ampersand
characters with &. Correct?

Thanks for your help.

Re: corrupted import file by via_newsgroup

via_newsgroup
Thu Nov 13 23:13:55 CST 2003

In microsoft.public.money, davetroyer@hotmail.com wrote:

>The & character is what's causing the corrupted
>download. Why is this not a problem with MS Money 2001
>and a problem with MS Money 2004?

I suspect it is/would be a payee you did not have in the other
statement. Money 2001 would have had the same problem.


> Anyway, I download the
>OFX file from the bank's website and it automatically
>imports it into MS Money provided MS Money is open. If I
>have Money closed how do I locate this file to do a search
>and replace of this ampersand character.

Expect to find it in the "My Documents" folder. But how do you know
that the ampersand is the problem if you don't know where to find
the file?

>
>Really this is the bank's issue to replace ampersand
>characters with &. Correct?

Yes. However you could modify the file yourself and do File->Import.
Then delete the statement within Money. That would be a temporary
workaround. Just pay cash to that merchant in the future.

>
>Thanks for your help.