I'm trying to chase a problem with a friend's Quicken setup. There's something wrong with her Vanguard IRA account. So, I decided to export it, create a new account, and import the data. File>Export says it will write a QIF file. File>Import says it no longer can read QIF files!
Can someone tell me how to get the existing transactions into the new account? Thanks.
> I'm trying to chase a problem with a friend's Quicken setup. There's > something wrong with her Vanguard IRA account. So, I decided to export > it, create a new account, and import the data. File>Export says it will > write a QIF file. File>Import says it no longer can read QIF files!
> Can someone tell me how to get the existing transactions into the new > account? Thanks.
On Fri, 31 Dec 2004 03:03:51 GMT, "Jim" <j...@nospam.com> wrote: >Intuit thinks you don't need to do this. Why would you evern want to import >your owen data into Quicken. Sillyness.
Contact Quicken support. They have some "magic" to help you out here.
>"William W. Plummer" <William.Plummer-NO-SP...@alum.mit.edu> wrote in >message news:HGXAd.828268$8_6.654257@attbi_s04... >> I'm trying to chase a problem with a friend's Quicken setup. There's >> something wrong with her Vanguard IRA account. So, I decided to export >> it, create a new account, and import the data. File>Export says it will >> write a QIF file. File>Import says it no longer can read QIF files!
>> Can someone tell me how to get the existing transactions into the new >> account? Thanks.
>>I'm trying to chase a problem with a friend's Quicken setup. >>There's >>something wrong with her Vanguard IRA account. So, I decided >>to >>export it, create a new account, and import the data. >>File>Export >>says it will write a QIF file. File>Import says it no longer >>can >>read QIF files! >>Can someone tell me how to get the existing transactions into >>the new >>account? Thanks.
> Wow, you sure don't read this group much, or even Intuit's long > stated intention to eliminate QIF file imports to Q2005 (except > for credit-cards - to be removed in Q2006, cash, asset, and > liability accounts).
> You can try importing into a dummy cash account, then copy/paste > the transactions from the dummy cash account into the desired > account. Q2005 is the first version of Quicken to allow the > selection of multiple transactions for cut/copy/paste.
> Or you can try just copying the transactions from the old > account, and pasting into the new account. This approach might > copy any corruption from the original account, so might not be > as good a choice.
Regardless, Quicken needs an export format that it can import. If it can read only OFX, then it needs to be able to write OFX.
I'll experiment with your multiple copy/paste suggestion. The problem she has is, even though she has only two securitys ("A" and "B"), she can only input transactions dealing with A. B is grayed out on pick lists and I don't see any obvious reason why. But more experimenting is needed.
Thanks for your assistance. I hope your New Year is prosperous and happy.
What a brilliant idea. Hopefully somone at Intuit is reading. You'd think some product manager with an MBA could figure this out without customer input.
> The problem > she has is, even though she has only two securitys ("A" and "B"), she > can only input transactions dealing with A. B is grayed out on pick > lists and I don't see any obvious reason why. But more experimenting is > needed.
Does she by any chance have a single mutual fund account set up? Have you tried making a new account?
For reasons I don't remember, I have single mutfud accounts like Fidelity Puritan *and* Fidelity Magellan, althoug they are both the same account number at Fidelity.
>> Regardless, Quicken needs an export format that it can >> import. If >> it can read only OFX, then it needs to be able to write OFX. > What a brilliant idea. Hopefully somone at Intuit is reading. > You'd > think some product manager with an MBA could figure this out > without > customer input.
Or maybe not.
In the first place, Intuit has already made it clear that they have no current plans to permit plain vanilla OFX imports; that is why your web-connect file has a "QFX" extension and not an OFX extension. Whether or not Intuit could construct a QFX export/import that would not intefere with their existing plans for downloads is debatable and if doable, may not be such a trivial exercise.
Secondly, as far as I know, OFX currently has no facility for such things as Categories, Classes, (possibly, transaction splits), Reimbursable business expense flags, Loan Schedules, Memorized or Scheduled transactions, Alerts, Asset Allocation, Tax Planning, Home Inventory and possibly more that I have not thought of.
OFX was not designed for the exchange of data between user data files, it was designed for the download of data from financial institutions to user data files. Whether it could be expanded to accomplish file-to-file exchange of data remains to be seen, even if for no other reason than that there are now a lot of players involved in the standard and I doubt that all those players have the exact same set of priorities, and some are actually competitors.
-- John Pollard First Last at Bellsouth dot net Please reply to newsgroup
>> The problem >> she has is, even though she has only two securitys ("A" and >> "B"), she >> can only input transactions dealing with A. B is grayed out >> on pick >> lists and I don't see any obvious reason why. But more >> experimenting is needed.
> Does she by any chance have a single mutual fund account set > up?
I think you have hit the nail on the head.
> Have you tried making a new account?
Should not be necessary; you can change a single mutual fund account to an account capable of holding multiple securities by clicking the word "Yes" in the Single Mutual Fund field in the Account Attributes on the account Overview screen.
> For reasons I don't remember, I have single mutfud accounts > like > Fidelity Puritan *and* Fidelity Magellan, althoug they are > both the > same account number at Fidelity.
I think it is *possible* that some fi's will want you to have single mutual fund accounts in Quicken if you have certain account arrangements with the fi. Might be one reason not to switch from a single mutual fund account; though a user should be able to verify this with the fi.
-- John Pollard First Last at Bellsouth dot net Please reply to newsgroup
>>> The problem >>>she has is, even though she has only two securitys ("A" and >>>"B"), she >>>can only input transactions dealing with A. B is grayed out >>>on pick >>>lists and I don't see any obvious reason why. But more >>>experimenting is needed.
>>Does she by any chance have a single mutual fund account set >>up?
You've got it, John. QIF is a full-blown file interchange format and QFX/OFX are strictly for transactions.
I guess the trouble from the bean-counters' perspective at Intuit is that you can use the QIF format equally well for transactions only. It's not quite as "intelligent" for that as the OFX format, but for customers and financial institutions who don't want to be constantly digging into their own pockets to enrichen Intuit for services that are mainly funded and supported by the financial institutions anyway, it gets the job done just fine.
Unfortunately by dropping support for QIF import in Q2005 Intuit has managed to toss the baby out with the bathwater. No more ability to share data files or do an export/import to clean up and salvage a file. At least with the ability to export QIF you still have the option to bail out to an alternative program without leaving all your data behind. I'm sure they'll correct that oversight in 2006.
...ken...
"John Pollard" <johnpoll...@bellsouth.net> wrote in message
>>> Regardless, Quicken needs an export format that it can import. If >>> it can read only OFX, then it needs to be able to write OFX.
>> What a brilliant idea. Hopefully somone at Intuit is reading. You'd >> think some product manager with an MBA could figure this out without >> customer input.
> Or maybe not.
> In the first place, Intuit has already made it clear that they have no > current plans to permit plain vanilla OFX imports; that is why your > web-connect file has a "QFX" extension and not an OFX extension. Whether > or not Intuit could construct a QFX export/import that would not intefere > with their existing plans for downloads is debatable and if doable, may > not be such a trivial exercise.
> Secondly, as far as I know, OFX currently has no facility for such things > as Categories, Classes, (possibly, transaction splits), Reimbursable > business expense flags, Loan Schedules, Memorized or Scheduled > transactions, Alerts, Asset Allocation, Tax Planning, Home Inventory and > possibly more that I have not thought of.
> OFX was not designed for the exchange of data between user data files, it > was designed for the download of data from financial institutions to user > data files. Whether it could be expanded to accomplish file-to-file > exchange of data remains to be seen, even if for no other reason than that > there are now a lot of players involved in the standard and I doubt that > all those players have the exact same set of priorities, and some are > actually competitors.
> -- > John Pollard > First Last at Bellsouth dot net > Please reply to newsgroup
>>>I'm trying to chase a problem with a friend's Quicken setup. There's >>>something wrong with her Vanguard IRA account. So, I decided to >>>export it, create a new account, and import the data. File>Export >>>says it will write a QIF file. File>Import says it no longer can >>>read QIF files! >>>Can someone tell me how to get the existing transactions into the new >>>account? Thanks.
>> Wow, you sure don't read this group much, or even Intuit's long stated >> intention to eliminate QIF file imports to Q2005 (except for >> credit-cards - to be removed in Q
