Hi guys,

I'm using BCP to import a CSV file into a database table, using the
following command:

BCP [Database].dbo.[Table] in "[CSV File]" -e "[Error File]" -T -c -t, -r\r\n

The import is working, but once imported, the first column of the first row
in the table begins with "n++". Very strange! I'm guessing this is an
encoding issue. Has anyone seen this before, and does anyone have any
suggestions how I can solve this?

Many thanks,

Steve.

Steve,

Weird response. I have seen unexpected Unicode values expand to 3 ANSI
characters in an OSQL script when the Unicode character is in a non-Unicode
script file. (A file without the leading 0xFFFE.)

(It doubtless depends upon the character and I do not fully understand what
is going one.)

Can you view your input file with a HEX editor and see if there is 1
(possibly invisible) character at the start of your file?

Definitely only FWIW,
RLF

"Steve Barker" <steve_barker (AT) nospam (DOT) nospam> wrote

Steve,

Weird response. I have seen unexpected Unicode values expand to 3 ANSI
characters in an OSQL script when the Unicode character is in a non-Unicode
script file. (A file without the leading 0xFFFE.)

(It doubtless depends upon the character and I do not fully understand what
is going one.)

Can you view your input file with a HEX editor and see if there is 1
(possibly invisible) character at the start of your file?

Definitely only FWIW,
RLF

"Steve Barker" <steve_barker (AT) nospam (DOT) nospam> wrote

Steve,

Weird response. I have seen unexpected Unicode values expand to 3 ANSI
characters in an OSQL script when the Unicode character is in a non-Unicode
script file. (A file without the leading 0xFFFE.)

(It doubtless depends upon the character and I do not fully understand what
is going one.)

Can you view your input file with a HEX editor and see if there is 1
(possibly invisible) character at the start of your file?

Definitely only FWIW,
RLF

"Steve Barker" <steve_barker (AT) nospam (DOT) nospam> wrote

Steve,

Weird response. I have seen unexpected Unicode values expand to 3 ANSI
characters in an OSQL script when the Unicode character is in a non-Unicode
script file. (A file without the leading 0xFFFE.)

(It doubtless depends upon the character and I do not fully understand what
is going one.)

Can you view your input file with a HEX editor and see if there is 1
(possibly invisible) character at the start of your file?

Definitely only FWIW,
RLF

"Steve Barker" <steve_barker (AT) nospam (DOT) nospam> wrote

Steve,

Weird response. I have seen unexpected Unicode values expand to 3 ANSI
characters in an OSQL script when the Unicode character is in a non-Unicode
script file. (A file without the leading 0xFFFE.)

(It doubtless depends upon the character and I do not fully understand what
is going one.)

Can you view your input file with a HEX editor and see if there is 1
(possibly invisible) character at the start of your file?

Definitely only FWIW,
RLF

"Steve Barker" <steve_barker (AT) nospam (DOT) nospam> wrote

Steve,

Weird response. I have seen unexpected Unicode values expand to 3 ANSI
characters in an OSQL script when the Unicode character is in a non-Unicode
script file. (A file without the leading 0xFFFE.)

(It doubtless depends upon the character and I do not fully understand what
is going one.)

Can you view your input file with a HEX editor and see if there is 1
(possibly invisible) character at the start of your file?

Definitely only FWIW,
RLF

"Steve Barker" <steve_barker (AT) nospam (DOT) nospam> wrote

Steve,

Weird response. I have seen unexpected Unicode values expand to 3 ANSI
characters in an OSQL script when the Unicode character is in a non-Unicode
script file. (A file without the leading 0xFFFE.)

(It doubtless depends upon the character and I do not fully understand what
is going one.)

Can you view your input file with a HEX editor and see if there is 1
(possibly invisible) character at the start of your file?

Definitely only FWIW,
RLF

"Steve Barker" <steve_barker (AT) nospam (DOT) nospam> wrote

Steve,

Weird response. I have seen unexpected Unicode values expand to 3 ANSI
characters in an OSQL script when the Unicode character is in a non-Unicode
script file. (A file without the leading 0xFFFE.)

(It doubtless depends upon the character and I do not fully understand what
is going one.)

Can you view your input file with a HEX editor and see if there is 1
(possibly invisible) character at the start of your file?

Definitely only FWIW,
RLF

"Steve Barker" <steve_barker (AT) nospam (DOT) nospam> wrote

Steve,

Weird response. I have seen unexpected Unicode values expand to 3 ANSI
characters in an OSQL script when the Unicode character is in a non-Unicode
script file. (A file without the leading 0xFFFE.)

(It doubtless depends upon the character and I do not fully understand what
is going one.)

Can you view your input file with a HEX editor and see if there is 1
(possibly invisible) character at the start of your file?

Definitely only FWIW,
RLF

"Steve Barker" <steve_barker (AT) nospam (DOT) nospam> wrote