|
PureBytes Links
Trading Reference Links
|
I have verified the findings of Lokanath. TC2000 exports v3 year 2000
data under the floating point format YYMMDD. -> so 01/03/2000 is 103.0
(000103.0)
For those curious, our software Byte Into The Market is reading these
dates fine. Tc2000 v3 data is still readable in our software. I have no
idea why omega and other software developers were not prepared. We were
prepared for this date to come thru as either 103.0 or 1000103.0. This
is not rocket science. I wrote about this back in december 99. Maybe 20
lines of code max.
Apparently both equis and omega have failed in this simple task. what
does that tell you? it tells me that when you have a software analysis
vendor who sells data there is a conflict of interest. you can't support
the reading of another data vendor's data. that is why omega no longer
reads tc2000 and metastock does not read tc2000, hardly anyone reads
metastock 2000 per dir....etc adnauseum. Open standards (ASCII)-open
interfaces (quotes-plus, quote.com) get kudos.
As an aside, we have been made aware of a number of usability problems
with our software on some monitors. In particular, there have
been problems with font readability on some high resolution monitors. We
are in the process of preparing an updated version with better user font
control and a number of other usability improvements, including vastly
improved right clicking, mouse wheel support, doubleclick listboxes etc.
I'll post a message when the improved trial version update is available
for download.
-- Tom Kohl (Tarn Software)
http://www.tarnsoft.com/
Lokanath Das wrote:
>
> Based on the data I received, TC2000 V3 seems
> to have the date as 00 just as you expect. But
> TS4 does not treat yr 00 as 2000. If that's the
> case, it will be a problem. Two solutions:
>
> 1. Ask Omega to fix this. I doubt if their Y2K
> claim work on any 3rd party data that are stored
> as 2digit yr. such as TC2000V3 & metastock.
>
> 2. Ask Worden Bros to write the date as 1000104.
> Since the date is written as floating number it
> might work for 16bit programs. But not sure.
>
> I haven't really verified case 2. I believe solution
> 1 should be the correct fix.
>
> I haven't tried reading these data in TS4 or TS2000.
> I will try this evening.
>
> Hope this helps.
>
> -Lokanath
>
> AOL
> 991221,86.0,88.0,84.0,87.0,17119400
> 991222,86.69,86.75,82.0,82.75,18324800
> 991223,83.88,85.5,80.63,81.0,15896100
> 991227,80.0,81.25,74.75,79.0,26018600
> 991228,78.0,79.13,76.5,76.5,14687000
> 991229,76.56,79.13,76.25,77.56,14638800
> 991230,79.38,79.56,76.38,76.5,13993700
> 991231,76.44,77.0,74.5,75.88,12985800
> 000103,76.0,83.38,74.75,83.25,32354500
> 000104,80.5,82.0,76.5,77.0,27020200
>
> SCMR
> 991221,266.13,287.0,257.88,285.25,382100
> 991222,288.0,305.25,265.0,296.0,458000
> 991223,296.0,306.25,288.75,300.88,388600
> 991227,302.25,302.63,289.88,295.5,329900
> 991228,295.75,327.0,293.75,316.13,266000
> 991229,318.88,326.0,312.0,314.0,73600
> 991230,326.0,328.0,290.25,299.88,130500
> 991231,298.88,315.0,292.0,308.0,123800
> 000103,312.25,322.5,290.0,311.38,361800
> 000104,303.06,304.0,292.25,296.5,234700
|