Stupid stupid stupid excel.
It always looks like it imports data right. It tries really hard to guess at how to import data and convert it. And then it runs into data like this:
Which, for some stupid reason, despite the quotes, it interprets as a number. Which it isn't. It's a zip code. In Puerto Rico. Which if you then copy-paste into SQL Server via Access linked tables (yeah, in a minute) you end up with 920 in the zip field. And if you a do a BETWEEN operator with that, you'll end up seeing Puerto Rico in the middle of Southern California.
Yeah, it's a long, stupid, non-integrated chain of user interaction to put the data into SQL Server, prone to lots of user error, plus all the"virus portal" programs like Excel, Access and Outlook (just missing out on Word for the 4-for-4 Office advertisement).
3 different users had 3 different problems, which were all this problem in 3 different tables where we store different addresses.
And the first person to recommend DTS as a "solution" for this gets knocked upside the head with a Louisville Slugger.