Thanks Dennis, This sounds promising, I will give your exit process a try. At these clients it is common for a user to walk away from a PC for an hour or more which triggers the timeout. Who knows what they were doing when they left the PC.
John From: [email protected] [mailto:[email protected]] On Behalf Of Dennis McGrath Sent: Thursday, July 08, 2010 1:46 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Session timeout I have found the same problem. Here is how I solved it. You will want to set timeout to 1 and watch the temp files for the session. They should disappear right away if you exit correctly. You can watch for them in the scratch directory when you open the test session. TIMEOUT.CMD is the file called when the timeout happens. --TIMEOUT.CMD --Code here anything you want to happen before the DB is disconnected CLOSEWINDOW - Just an example --End of code DISCONNECT QUIT TO EXIT.CMD RETURN - must have Here is the exit file --EXIT.CMD EXIT RETURN - must have Quitting cleans up any possible leftover nesting levels including IF/ENDIF blocks. Then you can EXIT and everything will be released immediately. Dennis McGrath _____ From: [email protected] [mailto:[email protected]] On Behalf Of Emmitt Dove Sent: Thursday, July 08, 2010 10:30 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Session timeout John, What action is taken on timeout? Do you: DISCONNECT EXIT We experience the problem of phantom connections seen by R:BASE if users lose their LAN connection or some other problem forces an untimely exit. The only way to clear all of these is to connect as a single user. Emmitt Dove Manager, Converting Applications Development Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of John Engwer Sent: Thursday, July 08, 2010 10:24 To: RBASE-L Mailing List Subject: [RBASE-L] - Session timeout Compiled vertical application Turbo V8 (latest available build) Desktop OS Mostly XP pro but some Win 7 and Vista Because of HIPPA requirements I have the session timeout set for 60 seconds in my vertical applications. In the startup file I have the following command [SET TIMEOUT 60]. I am finding that sometimes the connections do not time out as expected. When I issue (CVAL('CONNECTIONS')) it shows multiple connections active hours after the users go home. When I check the PC workstations it does not show the RBASE application active on any of the PCs. The only way that I have found to clear the orphan connections is to reboot the server. However, I have noticed that sometimes, the orphan connections clear as users start to logon the next morning. I would appreciate any comments or suggestions on this issue. John
