"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You just need to have one record in the text file with the incorrect size to trigger that error. You really need to check in all file which row has oversized values.

TylerSR. Data Systems AdministratorAuthor Commented: 2018-05-23

I loaded the file in excel then ran this value in a blank cell in the column =MAX(LEN(A1:A193199)) the returned results was this
9.00 8 so the field values are with in the tolerance, there is something that is causing this error and i suspect its an enomely in the way BCP is handling the FMT file upon the data file.

For a start, you are using field and row terminators, so dont be afraid to make your format file more flexible....
Secondly make sure your data file is clean and finished with the \r\n that you have told it (might have been something with the download, but it seemed as if I was missing a carriage return)
Third, make your receiving table more flexible - I often (if not always) import to a staging table first - just a plain table with a unique name.

Combines SolarWinds IP Address Manager and User Device Tracker to help detect IP conflicts, quickly identify affected systems, and help your team take near instantaneous action. Help improve visibility and enhance reliability with SolarWinds IP Control Bundle.

Yes, that can happen when the format file isnt flexible enough to accommodate the data elements - if too short it might not pick up the terminators and you end up with unexpected inclusions (such as '|') so the format file needs to consider all the characteristics of a field length - especially when delimited - you dont want it cut off before it gets to the delimiters.