MapForums
Community of VE/MapPoint Users and Developers
Possible Bug in MapPoint ?
This is a discussion on Possible Bug in MapPoint ? within the MapPoint 2006/2009 Discussion forums, part of the Map Forums category; Hi; I have developed COM Automation using Visual FoxPro. The code is "almost" the same as VB. In this module, ...
| |||||||
| Register | Blogs | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
09-16-2004
| |||
| |||
| Possible Bug in MapPoint ? I have developed COM Automation using Visual FoxPro. The code is "almost" the same as VB. In this module, when I use: PUBLIC goMapApp goMapApp = createobject("MapPoint.Application") goMapApp.UserControl = .T. && to get it out of memory when User EXISTS The instance of MapPoint STAYS in Memory after the User Exists, even when I RELEASE goMapApp. So, I can not reference the same MAP again, or make it visible. Once the User closes the MapPoint instance, its locked in, and I have to CreateObject again, otherwise it issues RPC Server is not available. So, I am forced NOT to make goMapApp public. Otherwise after a few times, the system resources are depleted. This seems to be a BUG, since according to the documentation, when UserControl = .T., it is supposed to unload it from memory, regardless of the controlling application. Has anybody come across this?         |
Linear Mode
