[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Metastock 6 and Y2k



PureBytes Links

Trading Reference Links


Just consider that the Reuteurs/Equis or Equis/Computrac Metastock data
formats were NOT Y2K ready before Equis finalized a format update : this
Y2K update was made available from Q4 1998 by Equis : MSFL 6.51 (Metastock
File Library for developers), next Metastock Pro 6.51... today 6.52.

Metastock 6 will fail to read this updated format from 1 Jan 2000
* The new (storage) format is number cyymmdd, the old was number yymmdd.
* Since c=0 for century 19, 4 Aug 1999 is number 990804 in both formats.
* Since c=0 for century 19, 1 Jan 1900 is number 101 in both formats.
* Since c=1 for century 20, 1 Jan 2000 is number 1000101 from 6.51, and not
valid in the old format.
* Metastock 6 does perform a strict validation of the old format (>999999
is invalid) => will reject Metastock 6.52 data from 1 Jan 2000 (and below 1
Jan 1900)

Not convinced ? Why don't you make a test in Downloader 6 ? - Add a
01/01/00 price record to a fake security. If the program complains about
"out of order data" before storing, then stick to the obvious = 01/01/00 is
the 01/01/00 of the prior data format(s) = 1 Jan 1900.

Feeding 1 Jan 2000 (6.51 1000101) into OmniTrader 3.5 or 4.0 does put it
into serious trouble, the date format validation check does not seem very
cautious.
As far as I remember, TradeStation 4 will show a 100 century in some
dialogs, however refuse to chart (again a strange validation).

Just for the record, Partech Parity 1.x validation check is yet another one
: they do consider the 6 rightmost (stored) digits only, and the charting
module does not check for out of order data => Year 2000 data in the
Metastock 6.51 format are charted correctly (1 Jan 2000, stored 1000101, is
read masked 101 before validation, then displayed 01/01/00).
This is, I think, the second scenario of Y2K support for read only
applications. Masked read + the (apparently) Microsoft suggested convention
of yy=30...99 for 1930...1999 and yy=00...29 for 2000...2029.

A lot of noise for a short conclusion : move to a Year 2000 coherent
application status, UPGRADE !

Alain
________________________________
At 04:37 3/09/99 +0300, Indy wrote:
>Hi
>
>I am using Metastock 6 but would like to know what would happen when
>downloading data after Jan 1, 2000. is it going to be impossible to
>use MetaStock 6 after that date or it will work but the date would be
>01/01/00?
>
>thx
>
>Indy
>