Hello everyone.

It has been a few years since I had a client that wanted a GPS / Mapping solution. My past project used vb6 and mappoint 2002.

I see many things have changed...was wondering if any one could give just some general feedback on which version of mappoint to use (I see 2006 has been released)....as for the actual program I plan on doing it in C#

Let me also state that the "mappoint web service" is out of the question, the client application may at times be in use where there is no internet connection.

Here are some things I am looking to accomplish...not sure if these are even "doable" with mappoint....if not any other software recomendations would be a huge help.

1 - Add dots (pushpins) with custom icons and change the icon to match the vehical state....possible show information in the pushpins tool tip.

2 - Basic routing and route information...a truck leaves new york at 9am and based on the current location, route, speed, should arrive in Detroit at 3pm...and the ability to make and compair different routes.

3 - Geo fencing - progmatically tell if a location (pushpin) is on a route or if the driver has left the route and is off sight-seeing.

Thanks in advance !

You should use MapPoint 2006 because it has updated data. There are some small programming interface additions as well, but nothing really significant.

VB6 is getting a bit long in the tooth. I've been trying some C# MP programming recently, and it works pretty well. I recommend Chandu Thota's " Programming MapPoint in .NET" book. This covers all the MP technologies, but the first section is for desktop MP and all the examples use C#. Combined with the MP help, you should have no problems.

Adding pins: No problem. Adding data to the text field in the balloon: no problem. You will have problems changing field data though (eg. data imported from a database).
Routing: No problem, but you can only do one at a time. Comparing routes will be limited because you can only display one at a time.
GeoFencing: Possible, but you'll need to experiment a little bit I think. Eg. you could look through the route segments, finding the distance from the pin location to each route segment.


Richard