does anybody help me to use the mappoint control in a VFP form.
When close the form I cannot close VFP an it appear the message cannot quit VFP
This is a discussion on Mappoint and VFP within the MapPoint Desktop Discussion forums, part of the Map Forums category; does anybody help me to use the mappoint control in a VFP form. When close the form I cannot close ...
does anybody help me to use the mappoint control in a VFP form.
When close the form I cannot close VFP an it appear the message cannot quit VFP
Can you deinstantiate or destroy the MapPoint object during the Form Close event?
Eric
~ Order MapPoint MapPoint 2013 Here and Get Free Access to the MapForums Downloads ~
~~
~ Upgrade to Get Access to the MapForums Downloads ~
PMFJI,
we had a similar problem and found that if you instantiate the Mappoint object and don't use it , it sometimes doesn't release properly resulting in the "cannot quit" message.
Trevor
But I use the control; I close the map and I remove the object in the container...Originally Posted by paradigm
... the result its the same "Cannot quit VFP"
There is a demo on using MapPoint and Foxpro:
http://www.mp2kmag.com/a43--charlie.....mappoint.html
Perhaps there are some pointers in there?
Eric
~ Order MapPoint MapPoint 2013 Here and Get Free Access to the MapForums Downloads ~
~~
~ Upgrade to Get Access to the MapForums Downloads ~
Originally Posted by palin
Did you ever see a solution for this? I get the same problem when I use the Mappoint ActiveX control (but not using automation, which is what the example by Fowler Software uses, so it does not apply).
Lew
We use MapPoint extensively in our VFP commercial applications and have found that the "cannot quit message" is usually related to object reference issues of one kind or another. We have also noted that in some cases you will need to issue "THIS.activemap.saved = .T." before the close of the map in order for it to release properly. You may also need to play with the VFP.AUTOYIELD parameter setting (depending on what you're doing).
Hope This Helps
Trevor
Try putting the command
ON SHUTDOWN QUIT
near the top of the program code
There are currently 1 users browsing this thread. (0 members and 1 guests)