- quote -

mostly Tax return checks which local municipalities issue
or the split of the taxes which was collect, but which
must be sent to the different school districts.

- quote -


- quote -

I'll try this and see, but money still does accept all of
the transactions.
- quote -

In microsoft.public.money, Steve W wrote:

- quote -

I have no experience trying to read in thousands of transactions all
at once. This is presumably a one-time event.


- quote -

Either. It seems to me that you would be able to isolate the problem
to certain records.

http://cbbrowne.com/info/financeformats.html may be useful.
- quote -

Well, if you try a test with only the first 10 records, do you get
the error? 20, 100? You may be able to figure out what Money does
not feel easy about.

Here's how I got the !Type:Bank.
I exported from Money the account I just imported using
the "As New or Recovered Account" option and compared
it to the QIF file I used to import in the first place.
The differences were that type line at the top of the file
with information about the opening balance and the years
of the dates as ^2003. I did both Strict and Loose.

When I say slow I am not talking about firing vi. I added
the line through NotePad, but the time it took to import
the same file "As a bank statement" into an empty account
compared to importing it into an empty account using the
"As new or Recovered account". The actual time until the
2209 transactions were imported and money gave me the
import complete message. I figured it was trying to do
some type of reconciliation with the file it now thought
was a bank statment and, as you pointed out, looking
for duplicates.

When you say to look for the record Money does not like
are you referring to the message I get about the file
being corrupted when I try to use the "As bank statement"
option" or the not a QIF file or the not the right kind of
transactions for this account messages I get when I use
the "As new or recovered account" option?

All of the transactions are imported when I keep telling
Money that "Yes", I still want to import even though it
thinks something is wrong with the file. This is during
the "As new or recovered account" option.

- quote -

In microsoft.public.money, Steve W wrote:

- quote -

New or recovered account does not check for duplicates.
- quote -

What do you mean by that? Are you saying it takes time to fire up vi
and typing that line in? Surely you can cat the required line to the
file.


- quote -

I would export a QIF file from the account in question. Examine that
file, and note the differences. You might try looking for a
particular record that Money does not like by working with a test
copy of your Money file, and importing stripped-down QIF files for
testing.


- quote -

Producing an OFX file would be a lot more work.

I have an UNIX program which creates a QIF formatted file
which I FTP over to Windows and then import. I have been
doing this in Qicken 98 for a while and am now thinking
about switching to MS Money. I've had no problems with
Quicken doing this. I've been working in Money 2003.

The accounts in Money are set up as checking accounts.

The transactions in the file are a list of checks to be
Printed.

When I do the import, if I choose the "As a statement from
my bank" I get an error saying the file is invalid or is
corrupted. If I choose "As a new or recovered account" I
get a message that the file does not appear to be a
Quicken file or is empty or does not have a .QIF extension
(which it does). Money does ask me if I want to import
the file any way and after picking the acount, Money tells
me that the file contains transactions for an account
that is not the same type as I'm trying to import
into. I can continue though and the import finishes fine.

I've tried adding a !Type:Bank line at the top of my file
and Money will let me use the bank statement option, but
the import that way is way too slow.

Is there something I need to add to the QIF file to get
rid of all the messages where Money is telling me I'm
doing something wrong, but lets me go ahead anyway?

Is there a different file type or layout I could be
creating to make this import smoother?

Thanks
Steve