Yes, the SDK can be licensed with a TIGER/Line based data set, or a Premium Data set based on the Tele Atlas Multinet data.  The TIGER/Line data cover the entire USA and the Premium Tele Atlas dataset covers the entire USA and Canada. Additional datasets for Mexico and Brazil may also be licensed for MapPro80.

* Note that the standard SDK package usually comes with Tele Atlas Data for the USA and Canada.  Any other datasets (Mexico, Brazil, etc.), including Premium Points of Interests need to be licensed separately.

Yes, MapPro80 comes with GPSPro.OCX an active-x control that allows interfacing to any GPS device using a physical or virtual COM port supporting NMEA sentences and to Garmin devices using the Garmin USB protocol.

No.  If you distribute copies of your application to others, or use it to track mobile assets, or create map images on a server to be accessed by others, or distribute printed copies of maps, you need the purchase the appropriate end-user license(s).  Contact UnderTow Software for additional details.

Yes, the map control has the ability to import multiple MIF/MIF or SHP files, under the user's/developer's absolute control. These are imported and rendered in the order specified by the developer. The map control also gives you the ability to define new street segments (and attributes like road type, name, etc.) at run-time, which may be automatically loaded, and used in conjunction with the core data sets. 

MapPro80 needs to know where to find the data files it needs to render the map(s) on the screen.  It gets this information from a set of properties, Path_States, Path_Data1, Path_Data2, etc...  When the sample code distributed with the SDK is executed, the app doesn't know where that data is located, so it cannot render the maps properly.  The user can either change the source code to set these properties, e.g., add code like,

or run the sample code and then select File, Configure and set the data folder locations through the program.

In order for the search operations to work properly, your application has to be pointing to the correct folders where the data is located and the DataSource property needs to be set to the appropriate value for the datasets you are using. If any of these are not set correctly, it's possible for some searches to succeed, while others fail since the OCX uses different groups of files, depending on the search operation.

If all goes well, when installing the program the process also registers the MapPro80.OCX and the GPSPro.OCX with Windows (using REGSVR21.EXE). However, before they can be used in a development environment, their interface needs to be imported in that environment.  That's how the IDE knows what functions, properties, etc belong to the controls, and how to access them.

The interface is imported when a control is added to the IDE's toolbox.  Unless that is done, the sample project is opened, but it has no way of interfacing to the OCX's functions and properties. 

One can modify the sample project code to dynamically create the instance of the OCX and import the interface, or a simpler way is to do the following:

1. Install the SDK from the Distribution DVD

2. Start VS-201 and start a new C# project (File, New, Project, Visual C#, Windows Form Application

3. Right Click on the Toolbox, select Choose Items

4. Select the COM Components Tab

5. Scroll down to locate MapPro80 Control (MapPro)

6. Make sure the box to the right of the name is checked and click O.K.  This should add the control to your Toolbox

7. Repeat steps 3,4,5,6 for the GPSPro control

8. Now, you can open the sample project and it should run