OK, I have to share (read "vent"). My company almost daily gets data to load into SQL Server, and it comes in Excel, because Excel has that nice table-like interface that makes it easy to enter, well, tables of data. Oh, if it were that simple. Excel is WAY too smart for its own good. Said data always has addresses, and addresses, in the US anyway, always have ZIP codes and ZIP+4 codes. They look like this: 01033-1234 A clever person will even select Format Cells > Text to preserve the leading zero. Why oh why for the love of all that is decent in this world can't the Excel datasource read that correctly, and when it can't, why does it not give some, er, ERROR MESSAGE or WARNING that it is stripping most/all zip codes out of your data and replacing them with NULL. Here's what I do to work around this stupidity, and I would LOVE a real solution: 1. Manually add another column to the incoming spreadsheet. 2. Insert a formula that adds some nonsense in front of the zip code, like =concatenate( "THISSHOULDBETEXT:", C2) 3. Fill down 4. Import my dummy column of data into a temp table, so the zip code is like "THISSHOULDBETEXT:01033-1234" 5. Use SQL substring() to strip the characters back off. This is enough, all by itself, to make me hate Excel. Grrr! Thanks for listening.