JWColby
jwcolby at colbyconsulting.com
Sat Sep 9 16:56:41 CDT 2006
I am using the import wizard to pull text files into SQL Server. Even though the wizard very clearly shows that the destination is to be [dbo].[etc].[conduit] it ends up creating [dbo].[etc].[conduit005] or [dbo].[etc].[conduit006] etc. Not all of the time, the first 4 times worked perfectly but then I end up with the ...005] table. Any ideas why, ever seen this etc? Now I have a ...005] which has no field names [field1], [field2] etc. All the data is in the table etc, but no field names because the origin text files did not have the header row. Is there any (simple) way to get this appended to the correct table. This table has ~400 rows so manually building an append query manually editing (aliasing) the field names to match is not an option. John W. Colby Colby Consulting www.ColbyConsulting.com