| Ability to process events resulting from an instance of MP
This article has enlightented us on usage of the MapPoint Object and controlling the object directly instead of using the OCX Control. We have been having difficulty in what we think is timing issues between the Mappont and our Access code being that the "Object becomes unavailable" even after checking the ReadyState of the control. So we want to investigate automating Mappoint directly and it appears this code sample does not have to check the readystate to run sucessfully.
The question that comes up is when using the Object this way, would the events available through the Mappoint Control OCX be lost? (e.x. SelectionChange event).
We want to be able to use the selected object (i.e. free-form shape or push-pin) that the user selected and process our Access data when the user clicks on a button on the parent form. We now use the SelectionChange event to keep track of the object selected. We can not see how they might be available yet.
Is there another way to determine the selected object? Do we have to go back to school on Access, Windows API and Object programming? |