Hi,

We're running an Acess 2003 FE with SQL2K BE. SQL resides on a Xeon
3.2g with 2g ram.

Many, many timeouts, and latencies that cause incorrect data to be
written or displayed or correct data not to be written/displayed.

It has been suggested to me that clients may be losing their TCP
connections, and I should use the Client Network Utility to ensure that
they are using TCP and not defaulting to Named Pipes (even tho our ODBC
connections are specified to be TCP only). That does not seem to be how
MS sees it. MS says you almost never need the Client Network Utility
except under certain specific conditions.

Any thoughts?

TIA,
Eric