Menu

#186 QIF import asks too many date questions

closed-wont-fix
nobody
importer (23)
5
2005-10-17
2005-10-16
No

I am trying to import accounts from Quicken 2004. When
doing so, I get the following popup:

"The date entry "2/18' 0" read from the file cannot be
interpreted through the current date profile setting of
"%d.%m.%yyyy".
Pressing "Continue" will assign todays date to the
transaction. Pressing "Cancel" will abort the import
operation. You can then restart the import and select a
different QIF profile or create a new one."

Problem is, when I press "Continue", it pop ups again
with a different date. It pop ups for each
transaction, and there are thousands of them.

This pop up should have a "Yes to all" button. It is
not feasable for me to migrate to kmymoney with this
implementation.

I am running the CVS version of FC4.

Discussion

  • Thomas Baumgart

    Thomas Baumgart - 2005-10-16

    Logged In: YES
    user_id=320825

    You should select the correct date format within the QIF
    profile (I expect it to be "%m/%d/%yy" according to your
    sample) which better matches the date format found in your
    file. This will also import the date as it is and not use
    todays date which is actually a quick and dirty way out of
    the situation not being able to interpret the date found in
    the file.

    If we're missing something, please let us know.

     
  • Thomas Baumgart

    Thomas Baumgart - 2005-10-16
    • status: open --> pending-wont-fix
     
  • ace jones

    ace jones - 2005-10-17
    • labels: 611721 --> importer
    • summary: QIF import asks to many date questions --> QIF import asks too many date questions
    • status: pending-wont-fix --> closed-wont-fix
     
  • ace jones

    ace jones - 2005-10-17

    Logged In: YES
    user_id=954547

    Right. "Yes to all" would be bad in this situation. The
    right thing to do here is just hit "Cancel" and fix the date
    format. As Tom says, please use %m/%d/%yy.

     
  • Hans Deragon

    Hans Deragon - 2005-10-17

    Logged In: YES
    user_id=148726

    As design goes, when I build GUIs, and there are error
    dialogs showing up, I try to implement the solutions within
    the error dialogs. If the date is wrong, why not offer the
    option to change the date format within the dialog error,
    instead of expecting the user has read the manual from A-Z
    and understood all the options before he starts?

    My rule when designing GUIs is to provide software that is
    so intuitive that I have no need to waste time with the
    documentation. The error dialog should explain what the
    situation is, why the current date format is wrong and how
    to fix it. In other words, in the error dialog is where the
    documentation should be, not on a website. And the user
    should be able to fix it on the fly, by pressing a button
    that opens up the other dialog that permits to change the
    format, or maybe by having the changing date format widget
    show within the error dialog.

     
MongoDB Logo MongoDB