Version: Quicken Classic Deluxe, R68.31, Build 27.1.68.31, Windows 11
Feature: File > File Import > Import Security Prices from CSV file
Summary:
When importing a CSV of security prices (format: Symbol,Price,Date, no header), the Date field is not being parsed correctly regardless of format used:
2-digit year (MM/DD/YY): Month and day are read correctly, but the year is always set to 2002, regardless of what 2-digit value is actually in the file. Confirmed with multiple different 2-digit year values (21, 24, 25, 26) all producing 2002 — this is not a century-pivot issue (e.g. treating "26" as 1926), the year value appears to be discarded entirely and replaced with a fixed default.
4-digit year (MM/DD/YYYY), and any other format containing a 4-digit year (tested: M/D/YYYY, YYYY-MM-DD, DD-Mon-YYYY, MM-DD-YYYY): the date fails to parse entirely. No error is shown — the row is silently imported using the "Date (if not specified)" value from the import dialog instead of the date in the file.
Critically, the import dialog reports full success in both failure modes ("Successfully imported N price(s)"), with no indication that dates were dropped or defaulted. If multiple rows in the same import share the same (incorrect or defaulted) date, only the last one survives — earlier rows are silently overwritten in the price history with no warning.
Steps to reproduce:
Create a CSV with several rows for one existing security, same symbol, distinct dates, e.g.:
File > File Import > Import Security Prices from CSV file, select the file, click OK.
Dialog reports success for all rows.
Open Investing > Security price history for that ticker.
Expected: entries dated 9/16/2026 and 9/17/2026.
Actual: entries dated 9/16/2002 and 9/17/2002.
Repeating with 4-digit years (09/16/2026) produces no dated entries at all for 9/16 or 9/17 — instead a single entry appears at whatever date was set in the dialog's "Date (if not specified)" field, with only the last row's price surviving.
Impact: Makes bulk historical price import via CSV effectively unusable for any data outside the current year, since there's no way to get a correct 4-digit year into the price history via this feature.
