MS Access and SQL Server

We're developing a new MS Access 2003 application using a SQL Server 2000
back-end. The workstation running Access is Windows 2000 Workstation, and
the server running SQL Server is Windows 2003 Server Std.

We've been developing in this environment for weeks, but suddenly we're
seeing intermittant failures in connecting to the database. For example,
there is an Access form with a combobox. When we run the form and click to
pull-down the list, we see the error:

ODBC -- connection to TSDATA failed.

where TSDATA is the name of the ODBC DSN we're using to link SQL tables.
This error occurs in a variety of other places in the Access program we
developed, but this is the only place where it consistently yields this
error.

One thing we recenlty did was to replace the SQL Server user in the DSN from
"sa" to another user we created for the application. We don't see how that
could have affected this issue.

Any ideas!?!?! Thank you!!!!!

Hi

You may want to monitor the server during periods when this is happening.
Use SQL profiler to see what is happening on the database and Performance
Monitor to check the server resources. Also check the SQL Server log and
Windows Event log for any information that may have been logged. You may
want to also post information on your SQL Server version.

John


"Dean J Garrett" <info@amuletc.com> wrote in message
 news:%23yKxXw%232FHA
.3868@TK2MSFTNGP12.phx.gbl...
> We're developing a new MS Access 2003 application using a SQL Server 2000
> back-end. The workstation running Access is Windows 2000 Workstation, and
> the server running SQL Server is Windows 2003 Server Std.
>
> We've been developing in this environment for weeks, but suddenly we're
> seeing intermittant failures in connecting to the database. For example,
> there is an Access form with a combobox. When we run the form and click to
> pull-down the list, we see the error:
>
> ODBC -- connection to TSDATA failed.
>
> where TSDATA is the name of the ODBC DSN we're using to link SQL tables.
> This error occurs in a variety of other places in the Access program we
> developed, but this is the only place where it consistently yields this
> error.
>
> One thing we recenlty did was to replace the SQL Server user in the DSN
> from
> "sa" to another user we created for the application. We don't see how that
> could have affected this issue.
>
> Any ideas!?!?! Thank you!!!!!
>
>
>
>