I use all of those, and many more, including ArcGIS, MapInfo, SAS, STATA - and I never get the same error as Maptitude. To be fair, I do not use the other GISs anywhere near as much as Maptitude. But I use SAS, STATA much, much more and neither of these products crash on me. Ever. The MS Office products (which I really do not like, but have no choice but to use) are stable, except Outlook which is real junk, software yo yo.  Mapt is nowhere close to that kind of performance. ... infinitely better.
 
I really wish Caliper would announce bug fixes, and allow us to download new versions and fixes. I think this would go a long ways in customer satisfication. All the non-GIS packages I use whether you have "Maintenance" or not do this. SPSS, SAS, STATA, MathStat, etc . Microsoft  and the GIS, Manifold.  
 
 
With due respect, "sending the error to Microsoft may be a better idea"    ???!!!
 
On a more positive note, I have had a great time with the 4.8 connection to TerraServer. I have incorporated this into two presentations and projects with significant usefulness. 
 
 
Richard E. Hoskins
 


From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Aniruddha Banerjee
Sent: Tuesday, July 18, 2006 3:09 PM
To: [email protected]
Subject: Re: [Maptitude] Re: Add line err:the Program referenced memory illegally

It's impossible to pinpoint operating system limits while using a software. Most errors that occur (even with programs like Mathematica, SPlus etc) due to the limits/failure of the operating system. Sending the error to Microsoft may be a better idea.
 
Rudy Banerjee
Berkeley, California

 
On 7/18/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

I have 4.8,  got oneof these messages last night. If I, say, use Maptitude over a week long period 4 hours/day I will get these messages about 3 times. Seems to come out of the blue and is usually not repeatable.
 
Maybe we should send a description to support everytime it happens, brief description of what was going on. Maybe Caliper can detect a pattern.
 
--
Richard E. Hoskins
 

 
-------------- Original message --------------
From: "mschoon2003" < [EMAIL PROTECTED]>

I get this error all the time (in Maptitude). It is often an issue on
the user's part (for instance, selecting an object that has 0's for
lat/long, etc), but sometimes just simply happens.

Whileit's a decent product, it's a shame that Caliper doesn't
write "defensive" code for those conditions that create errors, and
handle them more gracefully (and, ideally, LET THE USER KNOW WHAT THE
ERROR IS!!).

Save early and often!

Mike Schoonmaker


__._,_.___


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to