I just asked a friend to run the same code but on his machine that has MapPoint 2004 installed and he gets the correct distance.

So somewhere Microsoft has changed some default setting between 2004 and 2006 but only for the ApplicationClass. Drawing it onto the map still works and gives the correct distances.

This is really frustrating !!

I'll continue to look at the DriverProfile Settings.

// Michael

I have now checked DriverProfile settings and on both the Control and the ApplicationClass I have the same settings for PreferredRoads (0.5 for all).

The speed is however different.
ApplicationClass:
Debug.WriteLine(route.DriverProfile.get_Speed(GeoRoadType.geoRoadArterial)); --> 34
Debug.WriteLine(route.DriverProfile.get_Speed(GeoRoadType.geoRoadInterstate)); --> 70
Debug.WriteLine(route.DriverProfile.get_Speed(GeoRoadType.geoRoadOtherHighway)); -->40

Using the Map I get:
Debug.WriteLine(route.DriverProfile.get_Speed(GeoRoadType.geoRoadArterial)); --> 55
Debug.WriteLine(route.DriverProfile.get_Speed(GeoRoadType.geoRoadInterstate)); --> 113
Debug.WriteLine(route.DriverProfile.get_Speed(GeoRoadType.geoRoadOtherHighway)); -->65

But I don't see how the speed could affect anything since my problem is that I get the how this could affect the distance.

Now I'm getting really desperate.

Any help would be really appreciated /
Michael

Based on the relative speeds - it might take a different path.

E.g. imagine if Arterial and OtherHighway are both 20 mph, but Interstate is 200 mph, then given a choice it will be more likely to take the Interstate even if it is a longer distance.

Could this be the explanation?

Eric

Aah, I didn't think of that.

I'll try it right away and post my result here.

Thanks / Michael

I'm afraid that didn't do any difference.
I set the speed to the same values, but I still get the same result.

I'm now getting lots of complaints since the upgrade.

This is really strange

What more do you nedd when calculating the distance using the object library.
I've checked the coordinates and now I've checked the DriverProfile.

The calculation looks like:
Map map = MapPointApp.ActiveMap;
map.ActiveRoute.Clear(); //clear the route if one exists
Route route = map.ActiveRoute;
route.Waypoints.Add(fromLocation, "Start");
route.Waypoints.Add(toLocation, "End");
route.Calculate();
return route.Distance;

My last try looked like this:
Map map = MapPointApp.ActiveMap;
map.ActiveRoute.Clear(); //clear the route if one exists
Route route = map.ActiveRoute;
route.Waypoints.Add(fromLocation, "Start");
route.Waypoints.Add(toLocation, "End");

route.DriverProfile.set_Speed(GeoRoadType.geoRoadArterial, 55);
route.DriverProfile.set_Speed(GeoRoadType.geoRoadInterstate, 113);
route.DriverProfile.set_Speed(GeoRoadType.geoRoadOtherHighway, 65);



route.Calculate();
return route.Distance;

Regards / Michael

If it's any clue. All complaints I've got so far is that the distances are now to short.

Regards / Michael

Finally I figured it out.
The difference seems to be that the deafult value is now miles instead of kilometers like it was in 2004.

The strange thing was that this only seems to be the case when using the ApplicationClass and not when using the control.

map.Application.Units = GeoUnits.geoKm;

solved my problems, finally

Thanks for all the help that helped in the right direction.

Regards / Michael

Wow good work in solving that. It didn't occur to me..

Thanks!
It took me a long time to find it.
Partly because I trusted the documentation that says:

Units property

Returns or sets the unit of measurement used to measure distance; similar to clicking Options on the Tools menu. Default value is geoMiles in MapPoint North America and geoKm in MapPoint Europe.

// Michael