What file formats for Q2007?

I haven't used Q2007, but in 2006, you can import the QIF file.

I'm guess But you *can* import qif files into every account type in every version of Quicken through Q2006 ... and I believe Q2007 as well.

But not directly, right? Don't you have some magically methodology to do this? When I try, indeed Quicken DOESN'T let me import into Checking, for example. But that's because those accounts aren't available in the drop down list. So, I assume you must mean you can via some other fashion John?

I really am not trying to be cute here, but the average joe like me doesn't understand why you say this. I am, however, using Q2007 if that makes a difference.

Ok. Can I jump on you later? :)

I think Bob Wang has confirmed my suspicion: Q2007 is no different in this respect that Q2006 and Q2005.

I always thought that you read all the posts here. If you did, you would have seen that I have posted the way to do this before.

Andrew: you can not seriously be saying that just because you must now add a couple of simple records to the beginning of a qif file you want to import ... that I am saying something that is incorrect when I say you can import qif files into any Quicken account in any Quicken version.

Are you saying I was trying to mislead someone? I have posted the way to do the import in the Quicken forums; and I have posted it, or reference to it, in this newsgroup several times. I have never pretended that there was zero extra work involved ... indeed, when I comment on it I always say there is some (minor) additional work involved.

As far as I am concerned, those who say you can not import qif files to certain account types are (almost always unintentionally) the ones passing on the incorrect information.

I am at a loss to understand your complaint.

John - I wasn't complaining. I wasn't trying to be cute. I *was* trying to understand your comment that you can still do QIF imports. I do remember (that's the allusion to the "methodology") you mentioning some type of procedure here in the past so I wanted to make sure I knew what you were talking about.

I do see Bob Wang's reference to

in a later post on the subject, so I am also enclosing it in this thread in case someone sees it and wants to know how, since, although you said it was possible, there was no reference in this thread (I think) on how to do it. I'm fine now. I've saved the referenced procedure offline to keep it handy for the future. Thanks.

You forgot to include "as of today". Since Intuit has said that Quicken does not allow imports of QIF files into certain types of accounts they can -- at any time and without notice -- release an "update" that disables the import even if the account is specified in the QIF file.

Sometimes back doors are really trapdoors. Now if one was really paranoid one would think that a back door was left in deliberately to entice people that would not upgrade without it. Wait a year or two and then close the back door sending folks screaming to their FI's to pay the juice necessary to enable downloading.

The trick is to keep the charges to the FI's just below the po>Charlie K wrote:

I think my statement more accurately descibes the situation, as it doesn't include any paranoid speculation. Many things are possible, but I work with what's true here and now.

And even if Intuit created a new release for your Quicken version, you would not have to accept it. You can run any release of any version you choose.

[FYI: it was Intuit that posted the fact that importing to checking, savings, investment accounts was still possible in versions later than Q2004.]

Then you lose the online imports for your other accounts.

But they didn't say they would c>Stewart Berman wrote:

430 No such article 222 15649 body

Then you lose the online imports for your other accounts.

But they didn't say they would c>Stewart Berman wrote:

What the hell are you talking about? I said "release" not "version". Do you understand the difference between a "release" and a "version"? Rejecting "releases" to a version you already own will not lose you any ability to download anything; actually doing so can guarantee that such capabilties can not be removed.

But we were not talking about "Quicken downloads"; we were talking about downloads that occurred outside of Quicken (qif file downloads) ... which were then "imported" into Quicken. There is absolutely no way that Intuit/Quicken can prevent you from download qif files to your pc.

So: the issue must be limited to what Intuit can prevent you from "importing" into Quicken.

If you buy a VERSION of Quicken that can import qif files, there is no way for Intuit to *later* prevent that version of Quicken from importing qif files ... except by getting you to apply new RELEASES to that version.

So what? How many companies do you know that promise you what ever you want for as long as you want it.

You have not demonstrated any way that Intuit can prevent your existing version of Quicken from doing anything that does not require internet access *via Quicken* ... if you do not accept any (or some) additional "RELEASES" for it. And if you can't do that, you have NO case.

The burden is on you to demonstrate how Intuit can do this. You haven't even come close to doing so. You are wrong!

Sorry, I misread it. However, you would not know if the release turned off QIF file updating until after you accepted it. It could also be set to turn it off three months after it is applied.

Quicken is at a point where it cannot expand it's FI paying base without forcing the issue. It is obvious that online updating is not worth the cost for many FI's. Quicken is using it's market share on the desktop to try and force the FI's to buy their online interface.

If they keep the back door >Stewart Berman wrote:

You can always revert to a previous release; Intuit knows that, so I can't imagine why they would bother modifying your program which they know you could overcome by reverting to the previous release.

Uninstall current and re-install, then apply only the releases you want...

(right, John?) vcard

: >> Sorry, I misread it. However, you would not know if the : >> release turned off QIF file updating until after you : >> accepted it. It could also be set to turn it off three : >> months after it is applied. : >

: >You can always revert to a previous release; Intuit knows that, : >so I can't imagine why they would bother modifying your program : >which they know you could overcome by reverting to the previous : >release. :

That's it. One of the reasons I always download and save all the manual updates for each Quicken version I have.

Noted long ago.

But I don't think it has anything to do with the workaround method; I get the same result when importing directly to a Q2004 investment account, with no added header records in the QIF file.

Not sure I understand what the goal was here.

Unfortunately, that web page as well as the other one often referenced in this news group says it "you may not get the option to review the transactions " instead of saying you will not get the option to review the transactions . Actually the other frequently sited reference simply says "it may not work with investment accounts".

If you know it doesn't provide the review option why do you say "MAY not" instead of WILL not.

(Side comment: I wonder which version of Quicken introduced this "bug" for investment accounts. Must have been about the time that Intuit was pushing brokerage houses to go to web connect or direct import.)

The goal was to bring in the transactions for a reconciliation.

I have a 401K account that I normally update via Quicken's direct import. Unfortunately, that appeared to have missed one or more transactions as the cash balance was wrong. (Quicken apparently does not check that -- only positions.) I wanted to go back and import two years of transactions and check them against the account to see what was missed. I do not know how to tell Quicken to do that (the lack of transparency is a real pain) and thought I could import the transactions via the QIF file into the Downloaded Transactions section which would then allow me to match them against the register. Hopefully, the missing transactions would show up as new.

Unfortunately, the work around doesn't work for >Stewart Berman wrote: