Show/Hide Toolbars

MPMileage for Maptitude

Navigation: Running MPMileage for Maptitude

Database Notes

Scroll Prev Top Next More

The following are notes specific to particular databases and interfaces.

 

 

Microsoft Excel

 

We do not generally recommend the use of Microsoft Excel with MPMileage. MPMileage is designed to work with relational databases. Although Excel can be made to look like a relational database, it is not perfect.

 

Excel does not support indexing and can be very slow for all but the smallest worksheets.

 

By default, Excel guesses at the field types. This can pose problems for numeric string fields such as US zipcodes. These look like numbers but should actually be strings. The same applies for other fields. For example you should use a text key for the primary key. Usually integers are sufficient, but Excel will report integers as floating point numbers. Floating point numbers cannot be used as primary keys.

 

 

ODBC: MySQL

 

MPMileage applies delimiters to all identifiers using the ANSI standard double quote delimiter. You must set MySQL (and/or the ODBC connection) to use ANSI SQL quotes rather than the MySQL default single quotes.

 

 

Maptitude: Data View

 

MPMileage reads all Data View data before processing. This will make it seem like MPMileage has paused before it starts processing actual routes. Due to this, and Maptitude application contention, it is currently recommended that Maptitude is only used for small datasets (e.g. less than a few hundred rows).

 

Data view coordinates can either be the conventional decimal degrees or Maptitude's own internal integer "millions of a degree". MPMileage determines the units according to the data type. Floating point coordinates are interpreted as decimal degrees. Integer coordinates are interpreted as being in millionths of a degree.