I had seen that article before, I'm now I'm walking through it. I noticed that the locations were already geocoded, so that's how the solution works. I did find a pretty interesting demonstration on YouTube about doing Geocoding in SSIS, but haven't implemented it yet. Took me a while to walk through it, but pretty good tutorial. (Just make sure you don't skip a step!) Super cool, because I'm trying to convince someone that Access is just not the tool for doing exactly what he does in the tutorial - mapping sales data. (Never mind the fact that Access has nothing like SSIS to do data imports and transformations).
Thanks for making me look at the tutorial more closely!
Now to figure out the Geocoding stuff a little better. Found an example on YouTube, and a website that will do small datasets, but the company I'm working with has several thousand addresses to geocode. (I used to use the YAddress geocoder, but that apparently no longer works... It had a ProcessAddress TVF that did the geocoding and returned the County each site was in.)