ALSO, make sure you have RETURN immediately after the EXIT command. I even have a file called exit.cmd EXIT RETURN
QUIT TO EXIT.CMD This absolutely closes all files cleanly before the exit, no stragglers left open, Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, June 23, 2011 10:56 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: disconnecting old database connections 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.
