Randy Yates wrote:
> Tim.Clarke@manifest.co.uk ("Tim Clarke") writes:
>
>
>>Whenever I get these I write a tiny "stuff one record in and tell me if
>>it errors" iteration. Just leave that running and get on with something
>>else productive.
>
>
> I think the point is, if the driver error messages were a little more
> intelligent (including some context) to begin with, then you (and a
> bazillion others) wouldn't have to take any extra time to begin with.
> It would be an instant "Oh, I see the problem."
As far as I see, it's MS-Access not the ODBC driver which rsports the
*Overflows*.
> It might also be helpful if the driver converted all records it was
> able to convert and not simply abort on the first record with an
> error.
Unfortunately the ODBC driver itself doesn't detect any error before
MS-Access calls SQLEndTran.
regards,
Hiroshi Inoue