Ok, I was gonng do the timeout thing, but maybe a disconnect would be better. I'll put it in the applications as an action before closing. Thanks, Patti
--- On Thu, 6/23/11, [email protected] <[email protected]> wrote: From: [email protected] <[email protected]> Subject: [RBASE-L] - Re: disconnecting old database connections To: "RBASE-L Mailing List" <[email protected]> Date: Thursday, June 23, 2011, 3:55 PM Mike: Patti's original email stated that the particular users are dialing in using a remote program, are exiting the application properly, but the server still shows open database connections. So TIMEOUT won't help her I don't think. Patti: Just a thought. However your application is exiting, make sure you do a DISCONNECT right before the EXIT just to add some assurance. Karen In a message dated 6/23/2011 10:53:08 AM Central Daylight Time, [email protected] writes: Patti: Are you using the TIMEOUT setting? This might accomplish your purpose. Per the comments in R:BASE Help: "Use TIMEOUT to shut down an inactive R:BASE workstation and exit to Windows after a set amount of time passes. A countdown only begins when R:BASE is waiting for a keystroke--not while R:BASE is processing commands or while you are entering data. This is a useful feature for automatically disconnecting idle R:BASE sessions for scheduled database maintenance. " If you add something like SET TIMEOUT 60 command to a user's startup file it will cause R:BASE to exit after 60 minutes if there is no KEYBOARD activity. Maybe that will help.
