Add export/import to/from text files for purpose of identifying and removing corruption

Rocket J SquirrelRocket J Squirrel SuperUser ✭✭✭✭✭
I suggest adding a feature that would export ALL the data in a Quicken data file to a set of humanly-readable text files, and a corresponding feature that would
import those files as new data into Quicken. (Attachments would need to
be exported/imported in their native formats.)

My production
data file is irreparably corrupted. I keep using it because creating a
fresh data file would be a huge amount of work. I work around the
corruptions when they occur because I know when and where they manifest
themselves.

If I could export all the data to a set of text
files, I could examine them in a text editor and possibly correct the
corruption. Then importing the corrected files back into Quicken as a
new data file would eliminate my corruption issues.
Quicken user since version 2 for DOS.
Now using QWin Premier subscription version on Win7 Pro x64.
4
4 votes

Not Planned · Last Updated

Due to the complexity of implementation, this idea is not currently under consideration, but it may be reviewed in the future.

Comments

  • UKRUKR SuperUser ✭✭✭✭✭
    edited October 2018
    Isn't that where the QXF file transfer format would come in, if the bugs in it could be fixed once and for all?

    A utility or function to unload and reload a Quicken data file, whether it contains damaged records or not, is sorely needed.
  • QPWQPW Member ✭✭✭✭
    edited August 2018
    UKR said:

    Isn't that where the QXF file transfer format would come in, if the bugs in it could be fixed once and for all?

    A utility or function to unload and reload a Quicken data file, whether it contains damaged records or not, is sorely needed.

    Isn't that where the QXF file transfer format would come in

    About the best you can say about the QXF format even if it worked perfectly is it is "better" than nothing.  But the main problem with it is that it is a "closed format" and as such there isn't any way for the person to try to edit the dumped data.  It is sort of like validate and repair.  If it works great, if doesn't, you don't even know why it doesn't.
  • QPWQPW Member ✭✭✭✭
    edited August 2018
    UKR said:

    Isn't that where the QXF file transfer format would come in, if the bugs in it could be fixed once and for all?

    A utility or function to unload and reload a Quicken data file, whether it contains damaged records or not, is sorely needed.

    BTW I voted on this but I think that snowball has a better chance.
  • miklkmiklk SuperUser ✭✭✭✭✭
    edited August 2018
    UKR said:

    Isn't that where the QXF file transfer format would come in, if the bugs in it could be fixed once and for all?

    A utility or function to unload and reload a Quicken data file, whether it contains damaged records or not, is sorely needed.

    Same here, I have been asking for any usable import/export that could handle rebuilding a file by account.


    Seems extremely unlikely.
  • mshigginsmshiggins SuperUser ✭✭✭✭✭
    edited August 2018
    UKR said:

    Isn't that where the QXF file transfer format would come in, if the bugs in it could be fixed once and for all?

    A utility or function to unload and reload a Quicken data file, whether it contains damaged records or not, is sorely needed.

    You can't get there with QIF? Or at least a good portion of the export/import?
    Quicken user since Q1999. Currently using QW2017.
    Questions? Check out the  Quicken Windows FAQ list
  • UKRUKR SuperUser ✭✭✭✭✭
    edited August 2018
    UKR said:

    Isn't that where the QXF file transfer format would come in, if the bugs in it could be fixed once and for all?

    A utility or function to unload and reload a Quicken data file, whether it contains damaged records or not, is sorely needed.

    I just took a couple of minutes to look at things ...
    The QXF file format appears to be encrypted and/or binary data. That means, one can't edit it to fix anything. :-(
    An unload file format that can be edited, similar to QIF, CSV or HTML would definitely be preferable.
  • QPWQPW Member ✭✭✭✭
    edited August 2018
    UKR said:

    Isn't that where the QXF file transfer format would come in, if the bugs in it could be fixed once and for all?

    A utility or function to unload and reload a Quicken data file, whether it contains damaged records or not, is sorely needed.

    The big stumbling block for RJS is going to be his security options.

    The QIF format has Grant/exercise and such, but it has nothing to keep track of security lots.  That is required for any option to be properly "connected".

    In my case about the only options I had were long closed employee stock options.  And in that case it really didn't matter.  But it would royally mess up any open options.

    Another thing that might come up rarely is if the person used splits in an investment transaction.  I'm talking about like a split transaction you would have in a non investment account.  It is possible to have them in Quicken, but the QIF format doesn't have them.
  • Rocket J SquirrelRocket J Squirrel SuperUser ✭✭✭✭✭
    edited August 2018
    UKR said:

    Isn't that where the QXF file transfer format would come in, if the bugs in it could be fixed once and for all?

    A utility or function to unload and reload a Quicken data file, whether it contains damaged records or not, is sorely needed.

    You can’t get there with QIF or QXF or any of the above-mentioned formats. Remember, I want this for the purpose of correcting data corruption. XML could work, though.


    But conforming to a standard format is unnecessary, and XML can get complicated. I want any form of plain text which, when imported, recreates the entire QDF file, accounts, attachments., transfers, investment lots, and everything else.
    Quicken user since version 2 for DOS.
    Now using QWin Premier subscription version on Win7 Pro x64.
  • QPWQPW Member ✭✭✭✭
    edited August 2018
    UKR said:

    Isn't that where the QXF file transfer format would come in, if the bugs in it could be fixed once and for all?

    A utility or function to unload and reload a Quicken data file, whether it contains damaged records or not, is sorely needed.

    I hear a lot of people WANT to win the lottery too...

    Frankly if I was the product manager I wouldn't authorize such a project.

    Dumping everything out like that and importing it back in would be a complicated time consuming projects, that would have a heavy maintenance cost.

    What's more they only people that could really benefit from it being in a text format so that it can be edited would VERY high skilled individuals.  For the average person it would be an invitation to support calls as they hacked at in and got bad results.

    So basically the feature would be very costly, and really only benefit a very small percentage of Quicken users.
  • Rocket J SquirrelRocket J Squirrel SuperUser ✭✭✭✭✭
    edited August 2018
    UKR said:

    Isn't that where the QXF file transfer format would come in, if the bugs in it could be fixed once and for all?

    A utility or function to unload and reload a Quicken data file, whether it contains damaged records or not, is sorely needed.

    I would pay extra for it, and show them my MIT Computer Science diploma to get it.

    There’s a non-technical, business reason for Q not to take on this idea. I won’t mention it, use your imagination.
    Quicken user since version 2 for DOS.
    Now using QWin Premier subscription version on Win7 Pro x64.
  • UKRUKR SuperUser ✭✭✭✭✭
    edited August 2018
    UKR said:

    Isn't that where the QXF file transfer format would come in, if the bugs in it could be fixed once and for all?

    A utility or function to unload and reload a Quicken data file, whether it contains damaged records or not, is sorely needed.

    It wouldn't have to be a text-format unload / reload method to try and ferret out data file corruption. I would be very happy to have a stand-alone data file debug tool  available to the programmers and Quicken Support Level 2 or 3 specialists so that they can intelligently see every single database record in a human-readable format. That would make it possible to identify and repair corruption and return a broken data file to service. It would also make it possible for them to determine if there's a bug in the Quicken code that needs fixing.
Sign In or Register to comment.