B
Brian
For another application instantiated via VBA in Access, is it possible to do
any of these:
1. Disable the Close button for that application, or
2. Capture the processID of that application and later check to see if it is
still active, or
3. Check the current status (running or not running) of the that app
In particular, I am attempting to avoid being forced to trap & handle a
number of errors that can occur when a user closes MapPoint 2009 after I
instantiate it but before I retreive user-edited changes on the map for
updates to data in my Access app.
It would help if MS had made the MapPoint Control available in VBA with
MP2009, but alas, it is available only in VB 6, not VBA.
any of these:
1. Disable the Close button for that application, or
2. Capture the processID of that application and later check to see if it is
still active, or
3. Check the current status (running or not running) of the that app
In particular, I am attempting to avoid being forced to trap & handle a
number of errors that can occur when a user closes MapPoint 2009 after I
instantiate it but before I retreive user-edited changes on the map for
updates to data in my Access app.
It would help if MS had made the MapPoint Control available in VBA with
MP2009, but alas, it is available only in VB 6, not VBA.