Anybody else out there that's doing reverse geocoding with the Virtual Earth 6.1 API notice any wierdness last week with the VEMap::FindLocations method?  In short, we have several sites that grab address information based on a point from a map click, user coordinate entry, GPS location, etc.  Well, we were actively doing some reverse geocoding development for a client site last week when suddenly, all of our calls to the FindLocations method wound up returning null despite apparently well formatted requests with valid data points.  A quick check of our other currently running implementations revealed the same issue.  This appeared to be related to an automatic 6.0 to 6.1 upgrade that we received.  The quick solution was to switch certain portions of our code that called the offending method over to use the MapPoint web service so that we could at least continue development.  Meanwhile a quick call to Microsoft and the support folks confirmed our suspicions.  FWIW, Microsoft was very speedy in responding to the issue and all the folks we dealt with were very helpful.  We came in this morning to find renewed joy and love when calling VEMap::FindDirections...the issue appears to be fixed as we can get valid addresses in our result sets no problem.  Flipped the code switch off of MapPoint and back to VE API calls and all is well in the universe.  Still need to follow up with the MS folks as I'd really like to hear about the issue and resolution just for curiousity's sake.