|
PureBytes Links
Trading Reference Links
|
This is a quote from another forum, it might help some
of you cope with the '100' issue:
"Remember that ProSuite and EasyLanguage works in
Julian Dates, and the translation from Julian to
EasyLanguage date is little more than a formula. So
going from 991231 to 1000101 was almost a 'natural'
solution to the y2k problem.
===>Also, instead of trying to figure out the
EasyLanguage dates, I highly recomend you use the
ELDate() function instead of directly typing
EasyLangauge dates. The ELDate() function accepts
three parameters, so ELDate(1,3,2000) will return the
EasyLanguage date for January 3rd of 2000. By using
this function you avoid having to understand or know
about any EasyLanguage date formats rules or changes."
H
> -----Original Message-----
> From: Glenn Pederson <gpeder@xxxxxxxxx>
> To: omega-list@xxxxxxxxxx <omega-list@xxxxxxxxxx>
> Date: Saturday, January 01, 2000 5:52 PM
> Subject: Re: TS2000i SP3 Y2K Bug
>
>
> On 1 Jan 00, at 11:47, Glenn Pederson wrote:
>
> > I am running TS2000i SP3 with BMI datafeed and am
> getting a date
> > of "1/1/100" in the NewsMonitor this morning.
>
> Per a phone call with Omega Tech Support today,
> "1/1/100" is the
> format Omega has selected for their Year 2000 dates.
> Seemed like
> they wondered why I would see anything wrong with
> it. I guess I'm
> from the old school, because I have never seen a
> date written like
> this before.
>
> Happy 100 Everyone!
>
> Glenn Pederson
> gpeder@xxxxxxxxx
>
>
>
|