As it stands now, most locations that I feed MapPoint have fully resolved addresses but there are always those for which I have only a general idea of the area for any given reason - wasn't written down, not posted, or MapPoint will not recognize what is a proper address. For those, I play pin the tail on the MapPoint, and extract out the Longitude/Latitude using one of the available hacks to get the location in the right ball park. The problem comes when it's time to import the data in mass. If I map both the L/L & Address fields, it matches only for L/L. I have to reimport the same list twice using different field mapping settings to get all of the data onto the map. This still doesn't cut it however because, outside of being a PITA, the data cannot be analyzed as a whole. MapPoint will not recognize, for painfully obvious reasons I guess, pins from different sets when matched with different settings, as compatible for analysis. If I could find a way to collapse different data sets into one after matching, perhaps that would do. Much better, it would seem, would be to have the program sort it out on the front end.