|
PureBytes Links
Trading Reference Links
|
point 1 taken/in agreement
point 2 taken/in agreement/Equis should act on this
point 3 not taken/do not start questioning your software products AFTER a deadline has
been met, eg do this several months prior/upfront. Possible (Y2K) problems could
have well been forseen by running SOLID tests several months/well BEFORE
a (that Y2K) major happening is/was due.
After, and for secure reasons, you can than go into a "stand-by" modus, and let things
happen the natural way and possibly patch some unforseen incidents later.
This 'protective' procautions methodology has certainly not happened with the TC program,
of which questioneer is now left behind being the suffering party.
Regards,
Ton Maas
ms-irb@xxxxxxxxxxxxxxxx
Dismiss the ".nospam" bit (including the dot) when replying and
note the new address change. Also for my Homepage
http://home.planet.nl/~anthmaas
----- Original Message -----
From: Alain Jossart <Alain.Jossart@xxxxxxxxxx>
To: <metastock@xxxxxxxxxxxxx>
Sent: woensdag 5 januari 2000 17:34
Subject: Re: support
>
> Maybe what other people asked here some months ago.
>
> That their(Equis/MetaStock) latest data formats (2000 sec/dir and Year2000)
> be made public, and providing a free developer's kit without the current
> access limitations.
>
> This restricted access is a major reason why some preferred data vendors
> showed some incompatibilities with the Equis Metastock data format from 1
> Jan 2000
>
> Alain
>
> At 01:10 5/1/2000 +0100, A.J. Maas wrote:
> >Equis has supported y2k matters ever since early 1999 !!!!!!!, when
> >Equis dedicated itself to the Reuters Millenium-compliance Scheme,
> >which was than also made public............and with the 6.52a patch
> >and lately the $10 CdRom have kept their promise.
> >What more can one ask for?
>
>
|