QIF Date/Number import errors

Renan J. Felix rfelix86@ameritech.net
21 Dec 2002 10:30:14 -0500


--=-HNJv5WZJ6VdwJ1HA4aIU
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hello everyone! I am having no luck importing QIF files generated by my
bank (JPMorgan Chase). I have no problem with QIF files from credit card
companies or those generated by Quicken 2002 as I migrate. But my bank
QIF files will keep everything current but no luck here! As I try to
import the file I am greeted with an error message stating: "QIF file
parse failed: Data for number or date does not match a known format." 

I have read the QIF specs and I have read through the user and developer
lists so this comes as a surprise when I open and review the file.
Here's how it looks when I copy/paste:

!Type:Bank
D12/17/2002
T-18
PPURCH-SHELL OIL
^
D12/17/2002
T-7.57
PNYCE PUR
^
D12/17/2002
T+0.17
PIOD INTEREST PAI
^
D12/18/2002
T-70
PAUTOMATED PAYMEN
^
D12/18/2002
T-200
N00228
PCHECK # 00000228
^
D12/19/2002
T-300
PTO SAVINGS
^
D12/19/2002
T-130
PAUTOMATED PAYMEN
^
D12/20/2002
T-10
PPURCH-BP OIL
^

According to the mailing lists the number and date format should be no
issue. To the naked eye it appears there's no problem. Am I missing
something? I'll attach the QIF file in case anyone wants to try it. This
happens regardless of the GNUCash version. I've used 1.6.6 and 1.7.5
(yep, I know what I'm doing) and I compile from sources into a clean
install of Slackware 8.1 (a real distro!!). Any advise is welcome.
Thanks!

--=-HNJv5WZJ6VdwJ1HA4aIU
Content-Type: application/DEFANGED-45; name="activity_qif.DEFANGED-45"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="activity_qif.DEFANGED-45"

IVR5cGU6QmFuaw0KRDEyLzE3LzIwMDINClQtMTgNClBQVVJDSC1TSEVMTCBPSUwNCl4NCkQxMi8x
Ny8yMDAyDQpULTcuNTcNClBOWUNFIFBVUg0KXg0KRDEyLzE3LzIwMDINClQrMC4xNw0KUElPRCBJ
TlRFUkVTVCBQQUkNCl4NCkQxMi8xOC8yMDAyDQpULTcwDQpQQVVUT01BVEVEIFBBWU1FTg0KXg0K
RDEyLzE4LzIwMDINClQtMjAwDQpOMDAyMjgNClBDSEVDSyAjIDAwMDAwMjI4DQpeDQpEMTIvMTkv
MjAwMg0KVC0zMDANClBUTyBTQVZJTkdTDQpeDQpEMTIvMTkvMjAwMg0KVC0xMzANClBBVVRPTUFU
RUQgUEFZTUVODQpeDQpEMTIvMjAvMjAwMg0KVC0xMA0KUFBVUkNILUJQIE9JTA0KXg0K

--=-HNJv5WZJ6VdwJ1HA4aIU
Content-Type: text/sanitizer-log; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="sanitizer.log"

This message has been 'sanitized'.  This means that potentially
dangerous content has been rewritten or removed.  The following
log describes which actions were taken.

Sanitizer (start="1040484606"):
  Part (pos="903"):
    SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
      Match (rule="2"):
        Enforced policy: accept

  Part (pos="2322"):
    SanitizeFile (filename="activity.qif", mimetype="application/x-qw"):
      Match (rule="default"):
        Enforced policy: defang

      Replaced mime type with: application/DEFANGED-45
      Replaced file name with: activity_qif.DEFANGED-45

  Total modifications so far: 1


Anomy 0.0.0 : Sanitizer.pm
$Id: Sanitizer.pm,v 1.54 2002/02/15 16:59:07 bre Exp $

--=-HNJv5WZJ6VdwJ1HA4aIU--