|
Posted by wbertram on January 19, 2008, 11:11 pm
Please log in for more thread options You can use Yahoo Finance to download a .csv file of stock and fund
quotes. The file has price, date, and other data for stocks. The .csv
file is directly imported into Quicken and other programs, i.e., Excel
and Fund Manager, for example. I have been using this for several
years with no problems. An ICON on the desktop takes one directly to
the Yahoo download page. All stock and fund prices are available by 7PM
EST.
John Pollard wrote:
> MedRxMan wrote:
>
>> Open the exported file "prices.txt" by double clicking on it.
>> The
>> file opens with notepad. Now go to EDIT, Replace, then in the
>> find
>> field type the date you want to change and in the replace
>> field type
>> the date you want to use.
>> For example...I got and exported the prices today, 1/19/2008.
>> The
>> prices were actually for yesterday, 1/18/2008
>>
>> So in the "Find What" field i typed 1/19/2008 and in the
>> Replace With
>> field I typed 1/18/2008 then clicked OK and all the dates were
>> changed to 1/18/2008.
>>
>> I then opened Quicken 2008, went to Investment Center and
>> imported the
>> prices.txt file and it had the correct date of 1/18/2008 for
>> each
>> stock.
>
> I have no complaint with the workaround, but I suggest a much
> better long term solution.
>
> Ask the Netstock developer to provide the option to use the
> known date of the prices in the "Quicken" price file export.
>
> I believe the change would be trivial - the program already uses
> the "known" date for its other - non Quicken - price file
> export.
>
> When I suggested this to the developer, he replied that it was
> necessary to use "today's date" because he thought it was
> possible that some prices his program acquired could have dates
> that were "invalid" dates. This is not a legitmate reason for
> the treatment given ... though his other reason - that the
> product was "free" could be close to such a reason.
>
> My guess is that the change would be trivial ... but I do not
> have enough information to be sure that this is so.
>
> I think that if the developer knew that many Quicken users
> wanted the "known" date of the prices exported ... he might
> relent.
>
> [In fact, it should also be a trivial matter to determine if a
> date is a "valid" date ... in which case the application could
> then substitute today's date, or - better yet - refrain from
> exporting any price record for that invalid date.]
>
|