Marcus

You will probably find out it is the Banks problem but they most likely will
not fix it until someone points out where they are not meeting the
specifications of OFX. I would suggest

1) tell us the banks name and perhaps someone else can provide bank related
information
2) If you are so inclined, download the OFX specification or run the
Microsoft OFX analyzer that will tell what Money thinks is wrong with the
file. Report results to bank.
3) If you wish do edit the file to change account numbers you might then
post the file and perhaps someone on the newsgroup could identify the error.

Art

"Marcus Moraes" <Marcus Moraes[at]discussions.microsoft.com> wrote in message
news:4DA5B81A-B84A-4F80-8E2B-8A90B3ED028C[at]microsoft.com...
- quote -

In microsoft.public.money, Marcus Moraes <Marcus
Moraes[at]discussions.microsoft.com> wrote:

- quote -


Examine the file with a text editor. See if there are any
occurrences of the '&' character that is not part of this
five-character string: '&amp;' (or '&AMP;'). The presence of such a
character is one possibility.


You might also consider pasting the contents into a response. That
file will containing your account number(s) and financial
institution. Hide those by changing any number in the account number
to an 'n' character, and change any occurrence of a number in the
account number to a '#' character.

If you are sensitive about any balances or payees, you could make
the same substitution there. However the fewer such changes you
make, the more likely it is that

Or perhaps initially post the first part before any account number
and financial institution appear, such as these:

================================================== ====
OFXHEADER:100
DATA:OFXSGML
VERSION:102
SECURITY:NONE
ENCODING:USASCII
CHARSET:1252
COMPRESSION:NONE
OLDFILEUID:nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn
NEWFILEUID:nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn

<OFX> <SIGNONMSGSRSV1> <SONRS> <STATUS> <CODE> 0<SEVERITY> INFO</STATUS============================================ ===========================

which would be an OFX 1 file, or
================================================== =====
<?xml version="1.0" encoding="US-ASCII"?<?OFX OFXHEADER="200" VERSION="200" SECURITY="NONE"
OLDFILEUID="nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn"
NEWFILEUID="nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn"?< OFX> <SIGNONMSGSRSV1> <SONRS> <STATUS> <CODE> 0</CODE> <SEVERITY> INFO</SEVERITY========================================== =============================================
which would be the start of an OFX 2 file. The OLDFILEUID and
NEWFILEUID are probably not particularly sensitive, but their
contents don't add information needed to check things either. It is
not impossible that the FI use an account number as part of the
OLDFILEUID and NEWFILEUID.

The main thing here is to check that there is not some additional
data before the header, or some such.

Hi, I am having the same problem, and I have ran the file through the
analyzer, this is the response I get.
*** All line number references do not include header lines ***
***OFX 1.02 Add ~10
***OFX 2.0 Add ~2
Running Data Through Parser
No Parse Errors


"Steve" wrote:

- quote -

I appreciate any suggestions on this. I have Money 2007 and downloaded a
bank statement OFX file, but the following message keeps appearing:

"The file you attempted to import appears to be invalid or contains corrupt
data. Please download the file again. If the problem continues, contact
your financial institution".

I've already reinstalled Money, deleted the file and downloaded it again,
and it stills persists. My bank told me the problem is not theirs...but
Money's...

Any ideas ?

Marcus Moraes

Im willing to bet it is the banks not formating the data correctly try
downloading a QIF statement and see if that works if it doesnt run it threw
the OFX Analyser and see if you receive any parser errors OFX Analyser can
be found at the bottom of http://www.microsoft.com/money/fi/tools.mspx

--
Steve
steven_morrison69[at]hotmail.com



"Marcus Moraes" <Marcus Moraes[at]discussions.microsoft.com> wrote in message
news:4DA5B81A-B84A-4F80-8E2B-8A90B3ED028C[at]microsoft.com...
- quote -