-> On 08 Jun 07  19:27:00, mark lewis got back to Dan Ceppa 
-> Re: Hello!

 DC> Based on what i see in my non-standard setup, the time stamp
 DC> was/is the root of the problem.

 ml> yes, and the point that i'm trying to make is that the standard time
 ml> library code is at least one place that the fault occurs... 
 ml> generally, what is done is to take today's year and subtract the epoch

As it is, I had a similar problem with dBXL(dBASE IV).  

 DC> It's a shame I can't contact the people that created OMX.
 DC> They seemed to have guessed the Y2K deal and handled it
 DC> before it became an issue.

 ml> it isn't any majik, really... if one follows decent practises, one
 ml> won't fall into traps like this... 
 ml> why would you want or need to contact the OMX folk?

I'm not quite sure, but it seems to work as a Door for BW, albeit 
limited to 2 users.  With it, I never had the Y2K problem with BW.  
My messages prior to sending show a wrong date.  But, OMX handles 
them properly when it translates them into JAM format for sending.  

I've never had to avail myself with Dale's REP fix.  



... Bugs come in through open Windows...
--- OMX/Blue Wave/DOS v2.30