MapForums

Hy,

Has anybody found that closing the MapPoint ActiveX control is rather "dangerous"? I have found that on one system the application closed normaly (when closing the main form that contains the ActiveX control) but on other systems, the application hangs and refuses to close. I have to use the Task Manager to kill the process . I mention that i use MapPoint 2006.

What can i do?

Here is the code i use to open (start) the ActiveX control and the code to close it:

var Map1: TMap;

procedure StartMP;
begin
with Form1.OLEContainer do begin
DestroyObject;
CreateObject('MapPoint.Map.EU.13',FALSE);
DoVerb(PrimaryVerb);
OleObjectInterface.GetUserClassID(vGuid);
FMap := IDispatch(OleObject) as _Map;
with Map1 do
ConnectTo(FMap);
end;
end;
//--------------------------
procedure CloseMP;
begin
Form1.Close;
end;

I had this problem of getting MapPoint.exe to close when the VB.Net app containing the ActiveX control was closed.
The solution I found was to ensure that the CloseMap method of the ActiveX control was called in the form's Closing event. Then all went well!

Hy... But i don't have a CloseMap method... in the ActiveX control that is installed on Delphi there is no such method.

Hmmm. I'm using .Net and the control there certainly has CloseMap.
All I can offer is a link to the Microsoft MSDN Library where it is described:
CloseMap method
My .Net projects reference the MapPoint Control 13.0 (MapPoint 2006) via:
AxInterop.MapPoint.dll
and
Interop.MapPoint.dll

My problem is that CloseMap hangs and that's why I need to close Mappoint.exe. Here's the scenario:
We go thru a bunch of maps over and over and on occasion CloseMap just hangs. Currently it requires human intervention. We would like to be able to recover from this situation and close mappoint programmatically. I've tried numerous situations and none seem to be quite appropriate in this circumstance. Of note is the fact that there may be other programs on the server that are using Mappoint, so more than one MapPoint process may be running on the computer.

Anyone had similar problems and/or has a solution?

Thanks in advance

I'll have a play with that scenario (several MapPoint processes in use) and see what I can find out.
This is the code I use in VB 2005 (ThisMap is a MapPoint.Map, mp is an AxMapPoint.MapPointControl) :


If Not ThisMap IsNothingThen _
ThisMap.Saved = True ' Trick MapPoint into thinking it doesn't have to save the map.
Try
mp.CloseMap()
Catch
EndTry

Yep we do that (the saveMap I mean, either saving it or faking it out to think ie's saved), but sometimes CloseMap just dies out on us. Doesn't come back for the call for ages (overnight even).


Thanks in advance for your checking on it.

Well, I've tried running several copies of my app simultaneously, along with opening MapPoint in the normal way. All these processes closed down properly.
Sorry I can't be of more help.

I understand. Trust me replication has been a b*** for this problem. Sometimes you have to wait for hours for the problem to occur on a non-debugging machine. LOL

If anyone else has any ideas, I'm willing to listen.