[Ward C]

'peterlaursen' wrote:

Looks like an issue with the (Microsoft text-) ODBC driver then. We will have to check this.

But you could try to import using LOAD DATA syntax. Note that in that case the table structure must be created in advance.

I have done this with the table structure created in advance as well.. (ran once to create) modified table and then used to re-import.

I was thinking that it might be the driver.

but as I said even just changing column to varchar never solved the import itself. seems something is converting it to signed INT before INSERT

The data is not that critical to me as someone else is importing into oracle for a work around, but just thought someone should know to take a look at what is wrong.

Thanks, LOAD DATA worked fine.

[Ward C]

'peterlaursen' wrote:

Please try to map the column to a BIGINT during import.

I have tried that as well, even varchar 24, only imports up to that number, which is odd.

It is almost like it auto detects the column as int and will not override.

I have tried a numeric 17 zerofill.. and still yet that is the highest.

when opened with excel the largest number is 99380000001

Just for saying, the other columns that it detects as double does not seem to have this problem. This column which is auto detected as INT seems to be an issue.

[Author]

Posts