Hello, I wrote an application that invokes mappoint to display locations or calculates distance. I am running this application Server 2000 with people using terminal services. After awhile many sessions of the mappoint.exe is involked and it takes up all the memory and crashes the system. I have carefully gone over my code to ensure that I kill all the mappoint.exe sessions when I am done viewer or calculating the distance and I've been ensured that the users log off terminal services properly which should kill their session of the mappoint.exe, however, I still many sessions of mappoint.exe staying active. Has anyone encountered this problem or have a suggestion to handle this? Thanks

Hi,

Terminal service is a complete disaster It is nice to quick view remote some things but that's it...

We have a VB app that uses the MapPoint ActiveX control rather than launching MapPoint. We've been running this on Terminal Server 2003. As a stress test, we launched 15 sessions and had each session optimize a route with 220 stops on it. The test pegged the TS processor, but the system did not crash and all 15 routes were eventually optimized.

It may be more work than you want to do, but perhaps using the ActiveX control to display locations and calculate distances will take care of your problem.