Mappoint active x control crashes at random points

This is a discussion on Mappoint active x control crashes at random points within the MapPoint Desktop Discussion forums, part of the Map Forums category; hi,
we have an application that uses the mappoint active X control.. the customer uses it quite alot, however around ...

Mappoint active x control crashes at random points

hi,
we have an application that uses the mappoint active X control.. the customer uses it quite alot, however around 10 times aday when they bring up the form that is supposed to hold the mappoint control you just get a blank form and the app crashes.. i have logged my way through the code and it finds the locations ok and everything and its just when the form is shown (modaly) it will crash.. it doesn't do this all the time.. perhaps 10% of the time.. what they get is a form with nothing in it.. just a white (or black) square.. then our support team has to go in and kill the mappoint process and our app..

its running in a terminal server enviroment.. with 3 users.. 2 light users and one more heavy users..

please anybody, any thoughts.. this is becoming a real problem.. to the point where we might have to ditch mappoint and use another product..

Hi,
i am writting out to a log file every line of code that gets executed.. and when the code enters an on error resume next it prints out the err.description after every statement (only a couple).. not particular errors..

still just crashs randomly.. doesn't crash on any line of code.. just when the form is shown..

any more thoughts

i have looked at termainl server compatability flags and have had no luck..

I've found that MapPoint crashes randomly when I do some large batch process. For example, if I try to create drive-time polygons and export the drivetime coordinates (lat/long) to a file, the program will crash at different times (batch size of greater than 20,000 pts).

still just crashs randomly.. doesn't crash on any line of code.. just when the form is shown..

Can you tell me exacly what that you mean by "crash" because this word ican b used for one thousand situattions.. Also there is no 'randomly', there is happening something at that moment or a litle before. So it can be that the "crash" is some seconds later after a buggy code. Often this can heppen when overriding pointers.

Originally Posted by Chris Clarke

i have looked at termainl server compatability flags and have had no luck

Did you already test ouside terminal server so see f that has something to do with it ?

sometimes the form comes up with nothing in it.. i.e. its found the address and added the pushpin ok.. but when the form is shown it doesn't come up with the map.. other times it comes up with the basic map in the correct location but then freezes and doesn't draw the road names/pushpins..etc

I have no idea and never had that problems. Maybe this is a hint: Often while developping I interrupt the debugger, or I have exception errors (who doesnt and I stop debugging. If Itry then later start my application again it hangs "somewhere". If all mappoint instances are killed then all work fine. Note that this only happens when program terminate abnormally.

Can you check in task manager, when you have that problem, how many instances of mappoint are running ?

hi,
i thought it might of been this.. however there aren't any other mappoint processes running when it crashs.. we are running on a terminal server and i've tried giving each user there own database which doesn't make any difference..

Did you also try same application not on terminal server ? Regulary terminal server issues are poping up here, but I dont recall feedbacks on what solutions of problems where... _if_ it has something to do whit terminal server of course...