I don't have experience with Oracle, but it is very possible that Oracle is trying to save unused resources and it's kicking you out. That's something to review with your DBA.

On the other side, there are some timeout settings that you can define in you connection from within VFP. Check SQLGetProp and SQLSetProp functions in VFP help, there are timeout values for QueryTimeOut, IdleTimeout, WaitTime, ConnectTimeOut.



>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