Quote Originally Posted by XLGibbs
It is far better to qualify the required SELECT * INTO by breaking it into a
Create Table / Insert Into method.
Agreed; and perhaps I should have made my intentions clearer. I was really testing data conversions and how SQL Server handles field lengths - for example an Access char field that contains "12/07/2007 AM" should [and does] fail as a date/time in SQL Server. I am able to see this by manually going in under tasks/import, but was hoping SELECT INTO... would provide the same info.

I did however verify from another source that OpenDataSource() is buggy with respect to SELECT INTO.