Greetings,
As Tom pointed out, ODBC is old technology, and my guess is that Sql
Server 2005 is trying to migrate away from ODBC. The problem with ODBC
is that it is a continuous connection where ADO connects and disconnects
for each call. Most likely, these ODBC connection failures are really
"Deadlocking" issues. Not only does Access not deal with deadlocking -
it does not give a very informative error message.
Microsoft went all out to resolve the deadlocking problems with the
development of .Net (ADO.Net), and they did a real nice job. For a
multi user environment - deadlocking is always a major issue. With
ADO.Net, when multiple users hit the same table/record at the same time
- ADO.Net will set up a sort of qeue and gives a message (not too pretty
of a message - something about Transaction has been put on a qeue - but
the word "Failure" is not included in the message) -- you just click OK,
and your transaction gets processed next.
Rich
*** Sent via Developersdex
http://www.developersdex.com ***