nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Proper fromat for csv file to import security prices

MichaelCarr

Quicken Classic Business & Personal (Windows, Version R52.28, Build 27.1.52.28)

Building an import csv file to bring historical securities prices into a merged file created from two formerly stand-alone files (marriage). Following the instuctions in KB7150406 regarding deleting "!Type:Prices" and "^" from an exported QIF file creates two blank lines between each line that has data in it. Sample snippet:

"AKRIX",22.78,"10/31'14"

"AKRIX",23.38,"11/28'14"

"AKRIX",22.80,"12/31'14"

Do those blank lines need to be removed?

Find more posts tagged with

Comments

q_lurker

See this article - fifth bullet point arrow for acceptable formats. I don't believe the '14 for the year is appropriate. The blank lines should not be a problem.

https://www.quicken.com/support/how-do-i-import-data-quicken-windows

MichaelCarr

Thank you "q_lurker" - happy news about the blank lines. You are correct about the date format, the file did not have that operation completed yet.

Chris_QPW

Note the '14 for the year is the syntax used in a QIF file, it isn't correct for this use case. Quicken's QIF import accepts these two formats for years starting at 2000:

MM/DD'YY

MM/DD/YYYY

MM/DD/YY is for a year before 2000.

MichaelCarr

Chris, thank you. Interstingly enough, the first date format you mentioned is exactly what the QIF export provides, but to be safe I will converst all post 1999 years to /YYYY. Sincerely appreciate the assist.

Chris_QPW

Yes, Quicken's QIF export uses the 'YY format, but that isn't used for the CSV import. Which is a good thing since no other program uses that syntax to solve the year 2000 problem and most of the times people are going to be importing securities using a CSV file, they are going to be getting it from a place like Yahoo.

Side note, the QIF import of security prices is extremely slow, importing in CSV format is much faster.

MichaelCarr

Chris once again, thank you for the insight. After gettting the years all correct in my CSV, I noticed that the QIF export (and now my CSV) have embedded spaces instead of zeros in the MM/DD portion of the dates. Will that cause a problem or will they import correctly that way?

Chris_QPW

I don't really know if the spaces will cause problems or not.