Re: Ignoring duplicates in BULK INSERT with ADO and SQL Server 2000

What happened? It depends on the data. It will go to record number 1000
and then pop up a primary key violation, or it will say something
about data type conversion in record 7933.

The problem is not getting BULK INSERT to work. It works fine. The
problem is just that IF there is an error raised in the particular data
being processed, then it immediately stops and rolls back what it did.

When I read documentation on JET, it's pretty clear that this is
"normal" behavior for ADO, and to make it do something else you have to
use that "Global Partial Bulk Ops" connection parameter. I would have
thought that if there was something for JET then there would be
something for SQL Server. Apparently not.

Kevin

.