shahkalpesh
2008-12-12 20:56:50
A:
Its not an alignment problem and as my issue description states, I've tried to "store" the text as text (excel option) and I've tried to store it as general...
Frank V
2008-12-12 21:18:39
A:
It may be obvious, but is the destination string long enough to hold the string representation of the float? I'm not sure if Excel is rounding what it displays to you, so it may be worth trying with a wider column.
Meff
2008-12-12 22:38:56
A:
The answer has something to do with the fact that the procedure is expecting text but even if you set the properties (in the format dialog) to "text", excel may not handle the data as text. And hence, SQL Server (or the libraries) won't handle it to text.
When the procedures try to import it, the system feels that it is converting from a number to text and it expect that data maybe lost (even though no data will be lost) and the error is raised.
If figured out that I can get around this error by placing a ' (apostrophe) before each listed number. [I.E. '124321] This force excel to treat the number as text.
Hopefully this will save others the headache I now have from this. :-)
Regards,
Frank
Frank V
2008-12-22 17:04:17