I trying to execute this code thru a program compiled with XE5

Update TFTemp a
set a.CustID = (Select distinct b.CustID from DLCallRecs.LinesTF b
                 where b.TN = a.TFNumber)
where a.CustID is NULL

This is the error I am getting:

ElevcateDB Error #1101 The connection to the server at
192.168.1.4 has been lost ('Timed out while receiving stream')

The file has 194000 records to be updated.
When I run this code thru the EDB Manager it runs fine.
what can be the cause.

Ben

Ben


Try setting RemotePing to TRUE for the session doing this.

Roy Lambert

Where do I set that
ben

"Roy Lambert"  wrote in message
news:3D79E215-6CA2-4BDD-B74D-6912AC8D54D5@news.elevatesoft.com...

Ben


Try setting RemotePing to TRUE for the session doing this.

Roy Lambert

Ben


On the session component.

Roy Lambert

Remote Ping is set to true.  Its there by default

"Roy Lambert"  wrote in message
news:3D79E215-6CA2-4BDD-B74D-6912AC8D54D5@news.elevatesoft.com...

Ben


Try setting RemotePing to TRUE for the session doing this.

Roy Lambert

Its already set by default

"Roy Lambert"  wrote in message
news:7D9B33A7-8AAE-48CF-90BC-4D0A6547D5AA@news.elevatesoft.com...

Ben


On the session component.

Roy Lambert

Its already set by default

"Roy Lambert"  wrote in message
news:7D9B33A7-8AAE-48CF-90BC-4D0A6547D5AA@news.elevatesoft.com...

Ben


On the session component.

Roy Lambert

Ben


In that case

How long does it take the query to run?

What is your RemotePingInterval?


Roy Lambert

> How long does it take the query to run?  What is your RemotePingInterval?

EDB will NOT send a ping if you already have something running that uses the
communication layer to the server.     Try creating an event for the
OnRemoteTimeout of your remote session and set  StayConnected:=True;  in the
event code.   This will prevent it from timing out during a really long
query.

---------------------------------------
Terry Swiers
Millennium Software, Inc.
http://www.1000years.com
http://www.atrex.com
---------------------------------------

Terry

>>Try creating an event for the
>>OnRemoteTimeout of your remote session and set  StayConnected:=True;  in the
>>event code.   This will prevent it from timing out during a really long
>>query.

This is a really useful tip, particularly if you are running slow PROCEDURES (like transferring files up to a server). I wonder how you deal with the problem of a properly stalled execution. In that case (i.e. remote server crashing part-way through a query / procedure) would the above method result in an infinite connection or does some other event then get triggered?