RE: [DUG]: Restoring Lost Connections

[Myles Penlington]

Title: Message

Doubt it. Normally DHCP will renew a lease on a IP address - ie it Never changes.   J, What version of ADO/MDAC is installed on the client machines? You can use the ADO version checker to find out. I would suggest that perhaps a later version of ADO may help. eg 2.6 sp2 or 2.7 sp1.   We used to get the 'General Network error ' type problems, it was never hardware and since moving to Win2k ADO 2.6/2.7 I have not seen it again. About the only way to get it now is to unplug the network cable.   Myles. -----Original Message----- From: Nello Sestini [mailto:[EMAIL PROTECTED] Sent: Thursday, 28 August 2003 10:26 To: Multiple recipients of list delphi Subject: Re: [DUG]: Restoring Lost Connections Is it possible a DHCP assigned IP address lease is expiring and your server address changes while you are using it?   I have no idea how well that gets handled - presumably you should (and probably do) have the SQL server assigned a static IP.   maybe worth a look though ...       -ns http://www.roserox.co.th     ----- Original Message ----- From: Jeremy Coulter To: Multiple recipients of list delphi Sent: Thursday, August 28, 2003 03:28 Subject: [DUG]: Restoring Lost Connections Hi All. As some of you may remember from late last week I put on a post about some issues that I thought were relasted to dodgy networking cable or a bit of dodgy hardware in out SQL server, and that progressed into Static arrays and all sorts. Ok, well, this has resolved some issues, BUT there is still a bit of dodgy hardware somewhere as sometime we will get lost connections still. SO, the user gets an error "Lost Conection" there something like that, and I have code that is MEANT to reconnect to the DB if it does diconnect, this is in an ADOConnection comp. but the code never seems to fire, and even if I try to trap the error using the ADOConnection comp, it still does not always trigger. BUT I should larify one thing. The forms are all static, and the error happens when the user tries to update or insert the data. The events are, press button, build SQL string, fire the query....its at this point that the user gets notified of the lost connection. I of course get panicy phone calls from users who dont want to loose their data etc. etc. etc. This sometimes only happens once a week, sometimes 2, depending on whats going on.   Anyone got some suggestions?   Cheers,   Jeremy Coulter     ------------------------------------------------------------------------ All email scanned with Nortons Antivirus 2003 ------------------------------------------------------------------------