I don't really know, but here is an idea. Oracle has a table called DUAL that has exactly 1 record in it. You could have a timer fire every 60 seconds or so that issues a SQLExec(lnHandle, 'select * from dual') which would negate any timeout that may be in place.

>We are using VFP6 SP4.
>
>We have a VFP6 web based application running with West-Wind web connect. The application has been running great for years now.
>
>We just added a module to our application to access data in an Oracle database. This also works great.
>
>The problem we have is that after a period of inactivity, we seem to lose our Oracle connection.
>
>The way we normally get our connection to the Oracle tables is by issuing the following in our startup.prg:
>
>***
>Public gnconn
>gnconn = SQLCONNECT('mydatasource', 'userid', 'password')
>***
>
>This works fine, except that we seem to lose the connection to the Oracle tables after some period of inactivity.
>
>I have a routine to re-establish the SQLCONNECT(), but is it normal to lose your connection to Oracle after a period of inactivity?
>
>How can we ensure that we have a valid connection to Oracle at all times? We normally issue SQLCONNECT once at startup. I would like to avoid issuing an SQLCONNECT() with every request(unless that is standard practice).
>
>Or is this an issue to discuss with our Oracle DBAs? Could there be a timeout on our userid and password into Oracle?
>
>Thanks,
>
>Jerryt