Neil (nospam@nospam.net) writes:
> I mention the ODBC driver, especially in the context of multiple text
> fields, because it has been known to go to the wrong record when going
> to a record in a large recordset. In one application, I frequently would
> have the ODBC driver go to the record that was exactly 100 in sequence
> behind the one it was supposed to go to. I found that moving to the last
> record before going to the one I needed resolved the issue. I think it
> was fixed with a later patch, though.
>
> Come to think of it, I don't think that was a problem with the ODBC
> driver, but with the Jet engine, which was using the ODBC driver to
> access cs databases. So it could be a Jet issue, actually.

Yes, Access or Jet or something else that uses the ODBC driver could
maybe do something like that. But the driver on its own? That seems less
likely to me.

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx