Using the latest SDK for ADO, we've found a bug with the BCP code.
We can using the API to BCP into this table
Table : All pages locking
col1 int
col2 smallint
col3 int
col4 int
col5 datetime null
col6 varchar(255) null
col7 unsigned bigint
but as soon as we change the locking scheme to data rows the bcp fails.
But if we then add a null char field to the end of the table - the BCP api works again.
Table : data row locking
col1 int
col2 smallint
col3 int
col4 int
col5 datetime null
col6 varchar(255) null
col7 unsigned bigint
col8 char(1) null
Has anyone come across this bug ?
Will log it with support.