Board index MS SQL Server

ODBC timeout when connecting from ACCESS 97 to SQL Server 6.5 (heavy loaded server)

ODBC timeout when connecting from ACCESS 97 to SQL Server 6.5 (heavy loaded server)

Post by Bernd Rosen » Thu, 01 Oct 1998 04:00:00



Hi,

our ACCESS 97 application connects to SQL Server. When retrieving a
large number of records we sometimes get an ODBC timeout.
(maybe due to a heavy loaded SQL Server)
This sometimes makes it impossible to execute the query for quite a
long time (in some cases for several hours !!)

Where can I change the number of milliseconds when ACCESS timeouts the
query ?

May changing the query to ODBC direct or SQL pass through be a
solution ?

Please answer also by email.

Many thanks in advance for your help,

Cheers, Bernd.

 
 
 
Top

ODBC timeout when connecting from ACCESS 97 to SQL Server 6.5 (heavy loaded server)

Post by Jason Alle » Mon, 05 Oct 1998 04:00:00



> Where can I change the number of milliseconds when ACCESS timeouts the
> query ?

Access machine registry.  Search for 'JetTimeout'.  Default is 60 secs.

Cheers,

--


Phone: 04 1934 3588   (+61 4 1934 3588)
ICQ UIN=1533700

Out the 10Base-T, through the router, down the T1,
over the leased line, off the bridge, past the
firewall... nothing but Net.

"I refuse to short-change the 20th century to only allow it 99
years, the 21st century begins with the year 2001, not 2000."
Check this URL for details:
http://riemann.usno.navy.mil/AA/faq/docs/faq2.html

 
 
 
Top

1. Connecting to SQL Server 6.5 with MS Access 97 via ODBC

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 debugger 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 debugger 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

2. Connect once, use many

3. Connecting to MS SQL Server 6.5 via MS Access 97 and ODBC

4. set focus problem...

5. MS ACCESS 97/SQL server 6.5: deadlock problems when accessing server tables

6. Paradox SECURITY

7. MS Access 97 connect to SQL Server 6.5 Problem

8. Linux Largefile Support In Postgresql RPMS

9. access 97 -> sql server 6.5 via odbc

10. MS ACCESS 97/Sql server 6.5: deadlock problems when accesing server tables

11. SQL Server 6.5/ACCESS 97: deadlock problems when accesing server tables

12. Cannot access SQL Server 6.5 SP4 databases via Access 97

13. Import Access 97 data into SQL Server 6.5 using Transac-SQL


All times are UTC
Board index