SQL Server "Communication Link Failure" problem

I have an application written using VB 4 and connected to SQL server 6.5 SP4 through RDO 2.0.  (and ODBC 3.0).  The application is running OK except if I leave the application on and do nothing around 20 minutes and then back on again (for example, press a button to retrieve data) an ODBC  SQL driver error "Communication link failure" appear on the screen and I could not get any data.  I looked for the query timeout factor within the registry under ODBC but the timeout value is already quite generous..
Can someone give me a clue what's happening, please?  
waimanAsked:
Who is Participating?
 
connexConnect With a Mentor Commented:
There is also a timout-value in the configuration of the SQL-Server. If a connection is idle longer than that value the
SQL-Server ends the connection.

If you application is most likely idle for a longer time
i suggest closing the connection and reopen it when you need it.

0
 
waimanAuthor Commented:
I checked the server configuration.  "Remote conn timeout" is set to 10.  Is it the right parameter and if it is, what should be the right figure?
0
 
connexCommented:
Exactly that is the parameter. If you want to diasable it at all enter -1.
Else give the amount in minutes after that the server should
close idle connections.

0
 
waimanAuthor Commented:
I'll try that out first and I'll return to you later.  I'm going to be on holiday this month so I would hold this for a while but I'll let you guys know the progress next month then I will rate the answers.  Thanks a lot.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.