Frank This idea works nicely. It also solves the problem of a user that crashes out of a session (powered down, task manager, outage etc). When a table is used to verify in/out for the session and the user crashes out they become locked out of the application upon a valid return to it -- an issue I am trying avoid.
Thanks for the idea! Peter -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of Frank Taylor Sent: Thursday, October 30, 2008 7:22 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Mult-iusers, Multi-sessions, Mult-iPCs Peter, We use the RBase Plugin Rinstancecount.rbl to limit the users from opening more than 1 Session of R:Base at a time on their machines. Basically we look to see if there is another rbase session open, and if so, put a self timing form up saying the user already has a session of rbase open and then it exits. Here is a sample code of how we do that. Also I use the Cval ('computer') to allow certain machines to have multiple sessions (like myself) IF gcomp NOT IN ('OHARA235-ADMIN','OHARA234','OHARA267') THEN PLUGINS rinstancecount.rbl vrbg76|rbg76.exe IF vrbg76 > 1 THEN EDIT USING multiplealert EXIT ENDIF ENDIF The rinstancecount.dll will also work with other programs and code, which makes it nice in limiting the user from opening stuff you don't want them to. n Frank Frank Taylor - Information Technology Administrator F.J. O'Hara & Sons, Inc - Araho Transfer Inc. Boston, MA - Rockland, ME - Miami, FL Direct Dial - 617-790-3093 email: [EMAIL PROTECTED] From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Peter J. Ryan Sent: Wednesday, October 29, 2008 4:36 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Mult-iusers, Multi-sessions, Mult-iPCs We have several computers in a common counter area. Users loggin to apps to assist customers. Sometimes at their own desk Sometimes at the counter. Often at both places all day long. I am trying to find a way to limit the use of the same database being opened more than once on the same PC. Timeout option doesn't seem to be the issue -- its preventing the start of a session that already opened. (Re-training users and/or replacing the staff is an option desired but -- I really can't consider it now.) I guess mystartup.dat is missing sometime. Suggestions? _______________________________________________________________________ This Email has been scanned for all viruses by PAETEC Email Scanning Services, utilizing MessageLabs proprietary SkyScan infrastructure. If you need assistance, please contact the Systems Administrator, Frank Taylor at [EMAIL PROTECTED] - 617-790-3093. ** REMEMBER NEVER OPEN AN ATTACHMENT UNLESS YOU ARE SURE OF IT'S CONTENT AND SENDER ** _______________________________________________________________________
