I think this is the proper forum for this problem.
I have tried to import data from Excel 2003 into SQL Server. I have tried with 2005, 2000 and MSDE. I couldn't get this to work, so I imported a table with 1946 rows into Access and then into SQL. After getting past the field problems, the import engine finally successfully completed, telling me it imported all 1946 rows. But the first time the table only had 1 row, and the second time only 2 rows.
What's the problem? Either the SQL import didn't import all the rows and only thinks it did, or the data went somewhere else. Can any one shed any light on this problem? I am desperate at this point and can't figure out how to get the data from A to B to C.
Thank you for any help.
http://support.microsoft.com/Default.aspx?kbid=321686|||First of all, I did not appreciate the above comment. I don't know if this person is just trying to be clever or what.
Even though I have been programming, and have been in this business, for a long time, I consider myself to be a beginner when it comes to VB 2005 and SQL Server 2005, and therefore there may have been a reported bug in 2005 that I'm not aware of, or a more technical problem with importing data.
My workaround for this was to import from either Excel or Access and let SQL Server create a new table, and then write an Insert SQL command to transfer the data, and this worked just fine. However, I would still like the answer to the problem if someone knows what it is.
|||this -> "Read the 9th amendment. . . you moron!"
that's to the moron that is acting as our president. . . not you. sorry for the confusion!
the link is how to directly import into SQL server from excel using openrowset
|||Thank you for the clarification and the information.
|||you gotta love the internet! total loss of context!
cheers!
No comments:
Post a Comment