I saw this post by dterrie in the Wishlist thread and I just wanted to second it:
"How about bringing back a simple dBase import. The SSIS guys are clearly FAR out of touch with reality if they think people who handle data no longer need to work with dbf files. I've seen alot of dumb stuff in my day, bit this is just sheer brilliance. I just love the advice of first importing into Access and then importing the Access table. Gee, why didn't I think of such a convenient solution. I could have had a V-8."
I've been struggling with this the last couple days and finally decided to import the dBase III file into Access and then import that into SQL Server 2005. Imagine my surprise when I discovered this was the current recommended method.
That's just ridiculous. Can someone tell me why they would reduce some of the functionality of SQL Server from 2000 to 2005? This was a very easy process in SQL Server 2000...
Philip,
Could you record your request here:
http://lab.msdn.microsoft.com/productfeedback/default.aspx
That way a request will be passed directly to our bug system. It will increase a chance to address it sooner, and you will be informed about the progress.
Thanks.
|||Thanks Bob! That's a great idea.
I know you guys have been catching some flack over the anemic ODBC support.
Here's hoping there is a service pack for it soon!
