Microsoft Money Import using QIF file fails

[JSMWhitaker]

I'm try to import data from MS Money by creating a QIF file and then importing from that. Every time I try, MMEX shuts down. Reopening shows no rows imported.

Jim Whitaker

[JSMWhitaker]

UPDATE
I wonder if it is a problem with the size of the file; it has some 47k rows. I have created another file with only 160 rows and that has loaded OK. Is there a known size limitation?

[Nikolay]

There is no limitation.
Possibly there is not enough PC's memory for this operation.

[JSMWhitaker]

OK, I shall monitor that and see. 8Gb is usually not stressed by this sort of thing.

[JSMWhitaker]

I've tried again and there is no indication of significant memory use at all. Plenty of headroom in any case - 4.3 Gb available.

[Nikolay]

Could you reproduce the issue with mmex 1.3.5-rc.2 ?

[JSMWhitaker]

I'll try that.

[JSMWhitaker]

I discovered that I was using 1.3.5-rc.2 !
Changed to 1.3.4 - same behaviour, a large file crashes the application. Using a smaller file the import process runs but every record has an error and no records are loaded. The reported error is: "Error: Transaction Account is incorrect".

[Nikolay]

Could you provide QIF file sample?

[gooman]

Same problem here, importing large QIF file from Anmoney.

Crashes with no messages after 18200 lines.

I'm afraid I can't provide a sample - it's all highly sensitive info. Any way of getting any logging?

[Nikolay]

OK

Seems time to register the bug
https://github.com/moneymanagerex/moneymanagerex/issues
and generate QIF file with random data.
May be ubing Python script?

[njwmmex]

I had a similar problem - large QIF file exported from Quicken, crash on import into MMEx. Found the issue - not the size, but one record had a pound sign £ in the memo field. When I removed that the import was fine

[Nikolay]

Could you try to change QIF file encoding to UTF8?
Related bug:
https://github.com/moneymanagerex/money ... ssues/2751

[njwmmex]

Could you try to change QIF file encoding to UTF8?

The import with the £ sign in it now imports correctly in version 1.5.3 64-bit with the default encoding

[Renato]

Thanks for the feedback