MapInfo 64 Bit and VB6

[Graham Mitchell]

Hi,

I have an application that runs with MapInfo runtime 12 (32 Bit)

(Calling line to set up   Set Mi = CreateObject("Mapinfo.Runtime"))

I have installed MapInfo 15.0.2 (32 Bit) and 15.2 (64 bit) evaluation copies.

In VB6 I used the calling line to set up    -   Set Mi = CreateObject("Mapinfo.Application") for the 32 bit version.

Running up the VB6 program under the IDE and it all works fine.

I then changed the setup call to  -  Set Mi = CreateObject("Mapinfo.Application.x64") the IDE hangs when loading the MBX file

(MapBasics) though clicking away from the IDE the allows it to continue!

But when the program final comes up there are no maps shown.

Are there different DLL's?  is the calling method different?

I've just been given this to investigate which is my first time of using!

Thanks in advance.

Graham

[Stefan]

Hi Graham,

this behaviour has already been filed as a bug.

I had the same problem (https://groups.google.com/forum/#!topic/mapinfo-l/DEcgSVV7624) and finally got someone at PB convinced, that this is not as it should be.

There is a workaround:
The method that doesn't work with MiPro 64 Bit is "CreateObject", so if you start MiPro with a Shell-command and attach afterwards to the running MiPro instance, everything works as expected. But be aware, that even the shell execute comes back to your program too fast, so you should put in some wait-circles after starting MiPro, before attaching to the running process.

They say, that this bug might get solved with an upcoming 16.03 Patch or the next version 17 of MiPro.

Stefan

[Nick]

Graham,

I have had the exact same issue and have been in a situation where I am just unable to take advantage of using the 64-bit MI Pro.  

I will have to look at Stefan's workaround to see if I can implement the same type of workaround; however, I am glad to hear that I am not the only person that encountered this issue of a long delay when launching an MBX.

Please keep this thread posted if you hear of anything else that may help or of a bug resolution in the future.

Thanks!

Nick 

[DavidW]

I've also run into issues with VB6( using MapX) and MIv17beta.

When the VB program was called from MI, the search path for the dll's went into the MI v17 location first, so found the libspw_mi.dll there.

Consequently the 'FeatureFactory.IntersectionPoints' function failed.

This didn't happen with MI v16 64bit or any 32bit versions, so it was suggested I copy the dll into my application folder to ensure it found the correct version of the dll. Hopefully this will be solved in the final release.

Cheers