|
Posted by google on October 14, 2006, 11:15 pm
Please log in for more thread options Thanks again, John. It turns out that I had the csv format correct but
ran into a new (at least for me) Quicken bug. Quicken (2006) won't
import prices after there are 1,024 symbols (not prices) loaded. After
discovering this bug, I cut a number of my infrequently traded option
symbols out of the QIF export, converted the data to .csv format, and
finally got the prices for the less than 1,024 symbols to import.
Halleljah, I'm back to a near instantaneous transactions instead of 10
minute transactions due to shrinking my qph file. I'll post a little
more detail on this process next.
David
John Pollard wrote:
> > Thanks very much, John! I found the menu.
> >
> > Unfortunately, I can't seem to get my price import file into
> > the right
> > .csv format for the import to work. I've tried all the
> > combinations of
> > symbol,price,date I can think of, including surrounding each
> > one with
> > quotes.
> >
> > In case it triggers another thought for someone, what I'm
> > really trying
> > to do here is shrink my .qph file (because I'm experiencing
> > the problem
> > that Quicken uses 100% CPU for 10 minutes between every
> > transaction...which goes away when I delete the qph file).
> > I've been
> > exporting a QIF security list, deleting everything but one
> > price per
> > security per month, then deleting the QPH file and trying
> > (unsucessfully) to import the resulting manipulated
> > file...either as a
> > QIF file or a .csv file (with what I think is the proper
> > format in each
> > case).
>
> I don't think the QIF file export creates valid .csv file
> prices; I think it creates QIF file prices. You could try
> leaving the format intact and telling Quicken to import a QIF
> file instead of a price file.
>
> To see what one usable .csv format looks like, download a .csv
> file from Yahoo (I think they say "download to spreadsheet").
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML Sitemap