In the Virtual Earth AJAX control, there are certain screens that are somewhat hard to capture and control. The crux of the issue is using the “what” and “where” properties together in the VEMap.Find() method. When you do this, you’re actually using a different geocoding engine than you would be if you were to leave the “what” field blank using the same VEMap.Find() method.
Get Latest News
Subscribe to Digital News Hub
Get our daily newsletter about the latest news in the industry.