Anonymous
04-22-2004, 11:18 AM
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
Eric Frost
04-22-2004, 11:22 AM
Can you deinstantiate or destroy the MapPoint object during the Form Close event?
Eric
Anonymous
04-23-2004, 09:27 AM
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
palin
04-23-2004, 11:07 AM
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...
... the result its the same "Cannot quit VFP"
Eric Frost
04-23-2004, 11:50 AM
There is a demo on using MapPoint and Foxpro:
http://www.mp2kmag.com/a43--charlie.parker.foxpro.mappoint.html
Perhaps there are some pointers in there?
Eric
Anonymous
12-02-2004, 11:53 AM
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...
... the result its the same "Cannot quit VFP"
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
Anonymous
12-06-2004, 02:29 PM
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
Anonymous
12-06-2004, 06:59 PM
Try putting the command
ON SHUTDOWN QUIT
near the top of the program code