Unexpected EOF encountered in BCP dat-file.
If I just take a subset of the import file (about a 100 records), it imports
fine. I have deleted any extra trailing new line character (which stoppped
the transfer before). The BCP script that I'm using is:
bcp caltwindb..birthrec in F:\databases\sql\sqlbir1.dat /c /t"|" /r \n /e
F:\databases\sql\transfer.err /m100 /a4096 /Usa /SNORP1126
Can anybody help me with this problem? Are there limits to the sizes of
files that can be imported using BCP?
TIA
Nick-
Nick,
No, there are no upper limits. Run the bcp with a batch size of 1 so that you
can see which record it blows out on, then inspect the file with a hex editor.
There must be some extraneous characters in there.
Neil Pike MVP/MCSE
Protech Computing Ltd (MS Solution Provider)
Using Virtual Access 4.02 build 244 (32-bit) on NT 4.0 SP3