Very Computer

Hello,

to describe the environment briefly, we have MS Access 97 (Service Release 2)
which accesses the MS SQL Server 6.5 (Service Pack 5). Both, Server and Client
are installed on a Windows NT Workstation 4.0 (Service Pack 6). The computer is a
Pentium II 450Mhz CPU with 96Mb RAM.

The SQL ODBC driver was tested in an old as well as the current version.

Any assignments by program code (VBA) which expect an answer of the SQL server,
such as a .OpenRecordset or similar fail.
It seems as if the SQL server wouldn't follow with sending the data.
If one passes through these calls in the de* mode, then these usually work
straight off. One experiences the same effect, if one after a call is failed in
the code, passes through it directly in the de* mode once more.

If one changes the environment so that one evacuates the SQL server on a Windows
NT Server, then the same application works without Problems.

Can you help me?

Thanks in advance,

Sven Worm

Use SQL Profiler to determine what exactly is being sent to SQL Server then paste the code into Query Analyzer and see if it works or find the problem.

Alternatively turn on ODBC trace on the client computer and look at what SQL Server is returning when the problem occurs.  This can help you pinpoint error messages from SQL Server if your program doesn't return them.

Hello,

to describe the environment briefly, we have MS Access 97 (Service Release 2)
which accesses the MS SQL Server 6.5 (Service Pack 5). Both, Server and Client
are installed on a Windows NT Workstation 4.0 (Service Pack 6). The computer is a
Pentium II 450Mhz CPU with 96Mb RAM.

The SQL ODBC driver was tested in an old as well as the current version.

Any assignments by program code (VBA) which expect an answer of the SQL server,
such as a .OpenRecordset or similar fail.
It seems as if the SQL server wouldn't follow with sending the data.
If one passes through these calls in the de* mode, then these usually work
straight off. One experiences the same effect, if one after a call is failed in
the code, passes through it directly in the de* mode once more.

If one changes the environment so that one evacuates the SQL server on a Windows
NT Server, then the same application works without Problems.

Can you help me?

Thanks in advance,

Sven Worm