Our user accounts are limited to 10 sessions in our Oracle db. This is causing problems for users who are opening multiple sessions of Access and running multiple queries that include many linked tables to the Oracle db (they are running out of sessions). I found that Access was holding inactive sessions for 10 minutes. By editing the registry for the Microsoft Jet 4.0 ODBC settings ConnectionTimeout and QueryTimeout from the default 600 to 30 (Hex), I was able to drop inactive sessions after 1 minute (I expected sooner, like 16 seconds). I found the QueryTimeout property in the query as well, and reduced it to less than 1 minute. I can't seem to drop inactive sessions any before 1 minute and suspect there may be still another setting I've missed that is overriding.
Are there any other properties or settings anywhere else that I am missing or should review?
Thanks for any help you can provide...
Are there any other properties or settings anywhere else that I am missing or should review?
Thanks for any help you can provide...