We're using the MapPoint control in a somewhat unusual fashion, I suspect.

We have 2 VB.NET applications, both of which have one or more embedded mapPoint ActiveX controls.

The one that hangs periodically loads the form with the control, opens a map, does some operations on it, and then disposes the form. We do this because it's an "always-on" sort of app, and MapPoint has not been reliable enough to keep the control loaded 24/7.

However, if our other app (which keeps 1-3 MapPoint controls, each on separate forms) is running when this happens, it will occasionally cause the first app to hang while attempting to open the map.

Has anyone else encountered behavior like this?

Chris Rathjen