Glossary

Database

A database stores data. MPMileage uses an external database to read the list of routes to calculate and to store the results of these calculations. MPMileage uses the database in a relational manner, and works best when the database is an RDBMS (eg. Access or SQL Server). Other database systems can be used (eg. Microsoft Excel) but these can be very inefficient.

Data Fields

A Data Field is a particular value defined for each data row. For example a "Start Name" is a field that will be defined for every row.

Data Rows

Databases store data in rows. MPMileage expects each row to contain the information for one route to calculate.

Data Source

This refers to the specific database that MPMileage will use.

Driving Costs

The estimated costs for a route. These can be calculated using MapPoint's own cost estimates (based on speed, distance, and fuel efficiency) or using a user-supplied rate table.

File DSN

A File DSN (Data Source Name) is a Windows file that contains the connection information for a data source. These are typically created using the Data Sources entry in the Control Panel.

Location Names

The names used to identify start or end locations. These must be the names of pushpins defined in the supplied MapPoint file.

Map File

MPMileage requires a MapPoint map file (.ptm) file. This is used to define the locations of all the start and end points. Each point must have a pushpin with a unique name. These names are used in the database to refer to specific start and end points. A single pushpin can occur in many routes.

Microsoft Access

This is a relational database supplied as a part of Microsoft Office. Both MapPoint and MPMileage directly support Microsoft Access. Microsoft Access is recommended for desktop MPMileage usage.

Microsoft Excel

This is the spreadsheet system supplied as a part of Microsoft Office. Both MapPoint and MPMileage directly support Microsoft Excel. Microsoft Excel is probably the most popular data format used by MapPoint users. However, Excel spreadsheets do not perform very well with MPMileage. This is due to weak data types used in spreadsheets and the lack of any index facility. If possible, use Access or another true RDBMS system.

ODBC

ODBC is a cross-platform standard interface for databases. It is supported by virtually all relational database systems. MPMileage can also use ODBC connections to connect with databases either locally or on servers.

Overnight Stays

MapPoint routes can include overnight stays in the travel times. If selected, MapPoint will insert an overnight stay after every eight hours of travelling. Ie. eight hours of travelling becomes one day (24 hours).

Processing Threads

Modern CPUs have reached a clock speed limit. Therefore modern computers now contain multiple processing cores. MPMileage can utilize these extra cores by running multiple MapPoint instances. This option defines the number to run. The optimum will require some experimentation, but it will probably lie between N/2 and N-1 where N is the number of physical cores present.

Pushpin

MapPoint represents point data with a 'pushpin'. At a minimum, a pushpin has a location, name, and a symbol.

Rest Stop

MapPoint can automatically insert rest stops in a route at periodic times. Rest stops also have a fixed duration. Eg. "stop for 5 minutes every 4 hours".

System DSN

A System DSN (Data Source Name) specifies a data source that is defined within the Windows registry, rather than in a file. This is considered more secure, but it is harder to copy or manipulate.