Since most of us depend in some way shape or form on this product... why
don't we start forwarding this problem(which sounds serious) from the Top
Down...straight to either:
[EMAIL PROTECTED]
or
[EMAIL PROTECTED]
There's 2 systems at MapInfo for email boxes (that I know of anyway)....
But I agree....if you state that you are Y2K compliant then you shouldn't be
afraid to back your product up. Now In MapInfo's' defense....perhaps the
legal team hasn't done enough of a good job clearly stating that "should
something go wrong in a business decision.....someone will have to prove
that MI was at fault"...because as we all know....this is "lawsuit" country
(US) and from that perspective I can see why MI doesn't want to back certain
phrases........but never the less.... I think the legal team at MI needs to
come up with something clear as crystal.....
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Anitra Robertson
Sent: Wednesday, April 28, 1999 19:24
To: cj
Cc: 'MapInfo-L'
Subject: Re: MI Is MapInfo really Y2K Compliant?
CJ,
Our Y2K office has also had queries with MI's compliance statement. It
seems that it does contradict itself in some areas, and we have found MI
(in Troy) to be rather cagey about this.
As far as we are concerned, MI's compliance does not necessarily meet
our standards of compliance, but we are continually trying to find
answers, as this is the product of choice for us into the next century.
It seems we will have to wait for Y2000 to arrive before we will all
know!
Anitra Robertson
GIS Operator
Tattersall's Gaming
Melbourne, Australia
cj wrote:
>
> MapInfo says they're Y2K compliant, but are they really?!!!
>
> Even with it's quirks MapInfo has been the most productive option
> available to us. Now we're trying to upgrade both MapInfo and Map Basic.
> That's where the trouble begins.
>
> Recently, my purchasing dept. issued a purchase order to MI w/ a Y2K
> compliance warranty printed on it, written by the State Agencies legal
> section, that basically states the the company warranties their product
> is Y2K compliant and if it turns out it's not they will make it
> compliant. This warranty is stated on all state purchase orders to all
> technology vendors. In addition, MapInfo repeatedly assures us they are
> in fact Y2K compliant. YET, they have declined to accept the purchase
> order with it's warranty statement. In fact, they asked us to write void
> across the warranty on the PO and they'd send us the product.
>
> So are they REALLY Y2K compliant or not!!!???!!!
>
> The state agency I work for has been using mapinfo for several years no.
> We are one of only a few state agencies that have taken the chance on
> MapInfo, and continue to convert others. However, we will be forced to
> utilize other options such as ArcInfo/Arcview if we now have a product
> that we cannot upgrade, because the company won't warranty their
> software.
>
> Has anyone else run into this situation (knowingly anyway)?
>
> ----------------------------------------------------------------------
> To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
> "unsubscribe MAPINFO-L" in the message body, or contact [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]
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
