|
PureBytes Links
Trading Reference Links
|
Hi All,
On a related matter:
I just ran a test on SC V4.0 using the new MetaStock Year 2000 compliant
format ie the New DownLoader. I input data for the month of December 1999
and then January 2000. The result was that SC V4.0 worked fine except it
believes the Year 2000 is actually 100 - becuase all MetaStock has done is
to take the extra character in the date field and add a 1 in front of it for
Year 2000. Therefore, SC V4.0 is Year 2000 compliant with MetaStock format
as long as you understand 100 = 2000!!
Surely as CSI and MetaStock have now given the data format for post Year
2000 only a simple patch to SC V4.0 to clean up the century date is needed
not an entire new time delayed version 5.
Regards,
David Hunt
http://www.adest.com.au
-----Original Message-----
From: sptradr@xxxxxxxxx <sptradr@xxxxxxxxx>
To: omega-list@xxxxxxxxxx <omega-list@xxxxxxxxxx>
Cc: Melody.Blais@xxxxxxxxxxxxxxxxx <Melody.Blais@xxxxxxxxxxxxxxxxx>
Date: Monday, January 04, 1999 6:33 AM
Subject: Omega Server Y2K BUG Weirdness
>I posted a prior message stating that the TS 4.0 (19.6 build) server added
>Y2K futures contracts at the morning update and then would probably mark
>them as expired on the following morning update. It did. And then at the
>next morning update the server added the same Y2K cars again. Seems like
>the server is caught in an endless loop as worthless symbols pile up in the
>symbol portfolio.
>
>Since Omega has not provided a fix for this BUG, then the only solution
>would be to uncheck the morning update feature in the server.
>
>Okay, Omega, when do we get the patch to fix REALLY this BUG instead of
>using half wit solutions?
>
>-Tony Haas
>
>only 363 shopping days left to TS 4 meltdown....
>
|