Notifying dropped connections to MS SQL 6.5 
Author Message
 Notifying dropped connections to MS SQL 6.5


I'm working on an application that is attached to a MS SQL Server 6.5
via ODBC. The server will probably run on a Tandem redundant server, so
even in case of some hardware failure it should be available again within
a few seconds.

My problem is, that I want to prepare my app for dropped connections and
give them the ability to reconnect again automatically and start the last
task again.
I have lots of TQuery.Open- and TQuery.ExecSQL-statements so I tried the

  FOR i:=1 to 1000 do begin
    **create SQL-statement
  end;   // FOR
  on EDBEngineError DO ...

This works fine, if the TQuery-object isn't already connected to the DB
and tries to establish the connection automatically. The exception gets
called after a timeout.

If the TQuery-object was used before and the connection drops, I receive
a EDBEngineError-exception, but my exception handler is not called. No
further messages are dispatched to this application and I have to kill
the thread manually.

Has anybody else experienced this problems? Are there workarounds? Any
help is greatly appreciated!


Thiemo Sammern



Wed, 18 Jun 1902 08:00:00 GMT
 [ 1 post ] 

 Relevant Pages 

1. MS-SQL-Server 6.5 dropped to suspect

2. Connection dropped using DBMSSPX3.DLL and SQL 6.5

3. SQL 6.5 & RDO Dropping Active Connections

4. Dropping file system files after dropping database devices on SQL 6.5

5. how can sql mail (on 6.5) notify of low hard disk free space

6. Problem for connection to MS-SQL 6.5

7. Weird Connection To MS SQL Server 6.5

8. MS SQL 6.5 connection to ORACLE

9. DOS-connection to MS-SQL Server 6.5

10. Problem: Changing the User alials in MS SQL Server 6.5 for an active connection

11. Changing the User alias in MS SQL Server 6.5 for an active connection

12. Connection in Use (MS SQL 6.5)

Powered by phpBB® Forum Software