MPMileage 1.6 functions as a flexible and efficient program which helps you calculate mileages for point-to-point routes specified in a database. MPMileage can calculate distances, travel times, and estimated costs, with all results written to the input database. MPMileage supports all geographic editions of Microsoft MapPoint 2002-2010. Supported databases include Microsoft Access (1997-2007), Microsoft Excel (1997-2007), and ODBC connections.

Benefits:

1. Batch calculate thousands or even a million mileages.
2. Ability to calculate distances, travel times, and estimated costs at the same time.
3. Supports parallel processing for super fast processing on modern PCs.
4. Uses pre-located pushpins, allowing the user to QC and correct geo-location problems.
5. No need to upgrade from 2002: Works with all versions of Microsoft MapPoint from 2002 to 2010.
6. No need to convert databases: Supports most databases through ODBC.
7. No need to use a large database: Supports both Microsoft Excel and Microsoft Access.
8. Ability to select specific database rows for calculation.
   

Major Features:

1. Ability to take advantage of modern multi-core PCs.
2. Support for all of MapPoint's routing options.
3. Capability to calculate straight line distances, as well as route distances.
4. Support for various distance and time units.
5. Support for rest stops and overnight stays.
6. Walk-through tutorial.
7. Supports all geographic editions of MapPoint.
8. Works with the latest MapPoint 2010.
9. Windows Vista and XP are both supported.

1. Input data is read from a database
   • MPMileage calculates distances for point-to-point routes. Each of these routes is specified by a row in a database (typically Microsoft Access or Microsoft Excel). There are a wide range of possible applications, including: the calculation of delivery costs and times for individual customers; and the calculation of employee driving expenses.
   • This example database is based on an sample that is provided with Microsoft MapPoint. Notice that empty columns have been added to receive the distance, time, cost, and error status results. One of the results has been duplicated: MPMileage detects duplicate route requests and does not duplicate the necessary calculations.
2. Points are located with a map file
   • The individual points in the database are located using a MapPoint map (.ptm) file. Each location has a pushpin with a matching name. In this example, two pushpins have their information opened up for inspection. Although these example pushpins have lots of additional information, MPMileage only requires the pushpin's name.
   • By using pushpins in a pre-existing map, MPMileage does not have to worry about geocoding errors, such as mis-spelt addresses or mis-typed coordinates. This results in more efficient processing, because you do not have to run MPMileage multiple times to fix location errors such as these.
3. The results are written to the database
   • MPMileage writes the calculation results out to the empty columns in the input database. The error status indicates if the route was calculated okay or whether there was a problem, eg. if the source or destination location could not be located.
   • The output for the above example is illustrated to the right. No problems were found, so all rows are have their Errors column marked "Okay".

Enhancements:

• Ability to set the rest stop and overnight stay options
• Bug fix: Trial extension and purchased licenses not accepted under certain rare cases
• Bug fix: Unable to enter a file directory using the keyboard instead of the Windows File Dialog
  

• Microsoft® MapPoint® must be installed before you install MPMileage. MPMileage supports MapPoint versions 2002-2010. A suitable database is also required. MPMileage currently supports Microsoft Excel® (1997-2010) 
• Microsoft Access® (1997-2010); and ODBC connections. 
• The Microsoft .NET Framework 2.0 (or later) is also required.