Anonymous
09-16-2004, 06:50 PM
Hi;
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?
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?