View Full Version : VB6 .NewMap error since upgrade

12-11-2006, 05:44 PM
My applications that were developed using VB6 and MapPoint 2004 have been crashing with an error stating that MapPoint is not installed on the system since I have upgraded to MapPoint 2006.

When I check my references, MapPoint control 11.0 is selected (the path points to windows\system32\MappointControl.oca). [Edit: It is supposed to be version 13.0 I just realized, but it is not... I will try reinstalling MapPoint and see if the control's update]

There is, however, another reference with the same name that points to MappointControl.ocx. I suspect this may be the control I want to point to, but I am stuck:

I cannot uncheck the original control because VB says its in use. I cannot select the other control because it is named the same and causes a conflict (and thus, is not selected.

Everything starts up fine, but as soon as I call .newmap GeoMapNorthAmerica, I get an error.

Is there something I am missing here?

12-12-2006, 03:44 AM

Strange. If I register MP2006 the control's version is 13, and when I register MP2004 the automatically the control's version is 11 (after closing / restarting the IDE). Maybe remove and add again the reference to mappoint in the projects will help ?

12-18-2006, 11:33 AM
The uninstalling and reinstalling of MapPoint seemed to do the trick. Is it possible to register version 11 and 13 without having to install the respective products? I have the same question with Excel (clients use a range from '97 to 2003, and my application won't start on their PC's if I have not compiled the correct registered version it seems... but that is for another forum)

12-18-2006, 01:05 PM

Yes easy to do. I have done this by a bunch of batch files. Put a batch file in the appropriative folder where this is in:

MapPoint.exe /RegisterServer

You can do the same thing for al the automation programs with the several versions. In addition, if you have different compiles for different version you can change a class witch is linked to your applications that keeps the currently registered version.