<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><category>pcsoft.us.windev</category><copyright>Copyright 2026, PC SOFT</copyright><lastBuildDate>16 Mar 2017 16:32:21 Z</lastBuildDate><pubDate>16 Mar 2017 16:32:21 Z</pubDate><description>Greetings everyone,&#13;
&#13;
is there an easy way to make WD try reconnect when a physical connection to a Db is lost?&#13;
&#13;
I have next situation. I'm using OLEDB to connect to an SQL server db. When a connection problem occurs, WD throws an exception, which I'm able to trap. But, when I try to close the connection (declared by programming) , and reopen it, even if there's still no connection HOpenConnection will return True !? It seems that this approach won’t work. &#13;
&#13;
Now, I did try declaring a new connection, in which case, HopenConnection would act predictably (it would try opening, and after a while return False value). Although it could work, I would like to avoid this approach, because the code within whole application relies upon using initial connection defined as a global object.</description><ttl>30</ttl><generator>WEBDEV</generator><language>en_US</language><link>https://forum.pcsoft.fr/es-ES/pcsoft.us.windev/60676-sql-server-with-ole-access-how-reconnect/read.awp</link><title>SQL server with OLE DB access, how to reconnect</title><managingEditor>moderateur@pcsoft.fr (El moderador)</managingEditor><webMaster>webmaster@pcsoft.fr (El webmaster)</webMaster></channel></rss>
