🚀 go-pugleaf

Hm-m-m... ;-)

In Client/Server architecture (almost for all DB servers) it's by default no
activities from server side. In most cases only client initialize all
actions, therefore you should just "ping" your DB server to check "the
reality" of connection. Just create SELECT query for ANY table (it may be
dummy table at all) with MaxRecords parameter equal to "1" (and
CacheSize=1). DB access layer should generate an error if the connection to
DB lost. Catch the error in your code and process it. It is simplest and
reliable way.

Max

"newbie" <ms_Crack@yahoo.com> wrote in message
news:3e2eea88$1@newsgroups.borland.com...
>
> Hello all,
>
> I always evaluate if my ADO->connection is == true before performing a
query, however this does not always guarantee that a connection is in fact
enabled. If I disconnect a network cable after connecting to a database, the
connection->connected still is equal to true. Is there any other means of
determining if  a connection is truly connected, short of error handling on
a failed query attempt?
>