Yes , these problems are common . Transforming to a tab delimited is a good
idea.
You could automate this and set it up as a job - dts
--
Jack Vamvas
___________________________________
Search IT jobs from multiple sources- http://www.ITjobfeed.com
"scoots987" <scoots987 [at] gmail.com> wrote in message
news:7d46ad3b-34a8-432e-826e-1b884854b9be [at] s12g2000prg.google groups.com...
> What do others do if you need to import excel files into SQL Server?
> My main problems are
>
> 1) zipcode formatting issues. If the column is a mix of zip and zip+4,
> I have problems retrieving all zipcodes.
>
> 2) If the last column contains NULL no information is imported.
>
> All this with using the Management console using Import data in SQL
> Server 2005. I am simply trying to import the data into NEW databases.
> The excel files vary in structure. Right now I am working on case by
> case basis.
>
> Does anyone see these types of problems?
>
> What I am doing now is converting the excel file to a tab delimited
> file and that seems to work.
>
> TIA.
