This usually happens when that column is mixed with strings and numbers, Microsoft recognized it was a bug but provided no decent solution to it.
I tried to use SQL Server import, it has the issue. Tried ADO.Net, no luck either. Finnally came across a MS suggestion to add "IMEX=1" to the Excel connection string, and it worked.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment