Neil (nospam@nospam.net) writes:
> Thus, I'm wondering if there's a possibility that either the SQL
> database or the ODBC driver somehow shifted the data from one record
> into another. That seems far-fetched. But, at this point, since a table
> that the user didn't touch somehow had its data changed to data from a
> different record, I'm trying to explore all possibilities.

Since your description is very abstract, it's difficult to tell what
is going on, but the likelyhood that the ODBC driver would confuse tables
on its own is nil. The likelyhood that SQL Server would do it also very
small, but it could be a corruption issue. However, a corruption usually
manifests itself with violent error messages. But run DBCC CHECKDB on the
database to rule that out.

I would direct my attention to the application code. That is, the stored
procedures and the client code. Something may not be what you think it is.
--
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