We've recently upgraded a client because of this situation. The upgrade
was easy and painless. The Y2K issue is limitted to the Haht
Application Server, so if you are using ASP or some other application
server, you shouldn't be affected. I believe that the problem is with
one specific function that is used to convert two-digit date strings to
four-digit date variables. The function assumes that 00 reprents 1900.
I think that the upgrade solves this problem by converting anything
below 30 to 2000 dates and anything above 30 to 1900 dates. If you
don't use this function, then you shouldn't need to worry.
It is a bit annoying that MapInfo didn't find this until so late in the
year, but I guess the old saying still applies...Better late than never!
Gary.
Dick Hoskins wrote:
> I got a letter in the mail today dated December 17th from MapInfo
> stating that:
>
> "If you use the HAHTsite Application Server to perform date-related
> functions within your MapXsite and/or MapXtreme applications, this
> information may affect you. MapInfo has determined that the OEM
> version
> of the third party software, HAHTsite Applicaiton Server OEM version
> 3.1, builds 101 and 103, which was previously believed to be
> Y2K-compliant are indeed not Y2K-compliant without an upgrade. This
> application server is shipped with MapXtreme NT and MapXsite. HAHT
> has
> provided an upgrade, which MapInfo has modified and tested for its OEM
>
> version............"
>
> The letter then goes on to explain the situation in more
> detail Comments, etc? Dick Hoskins
> [EMAIL PROTECTED]
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
