View Full Version : Optimize stops mystery

09-07-2012, 06:40 AM
Hi all

I'm using MapPoint 2010 and have the following case:

Optimize different routes with 15+ stops created from lat-lon, using default driver profiles
and quickest route.

Optimize via activex method gives results with some strange detours here and there.

Importing EXACTLY the same stop data, same start and end point, same departure times,
same stop servicing time and same default driver profile settings in MapPoint Desktop app.
Optimize gives a near perfect result. 20-40% shorter and faster than through activex.

I have experimented with driver profiles, quickest/fastest and prefered roads. Same deviations
occur. I am begining to suspect the optimizing routine in desktop app is not the same as we
get in activex.

Anyone using mappoing opimization via activex with success out there?


Eric Frost
09-07-2012, 08:21 AM
Hmm, very strange, have you tried other versions of MapPoint (2006, 2013)?

Also, rather than use the ActiveX control, can you automate the desktop app to see what happens?

09-07-2012, 08:42 AM
To be more precise the mappoint ocx (activex) is only used for a map point UI control to be embeded in our app.
All other methods we use is automated from the distributed type library. So maybe I should try to automate
all from the ocx file and see if it makes any difference.