Bill, You could use the login table approach. IF vUserLoggedin THEN kick them out ENDIF
The problem I see with this approach is that there are times when a user is exited ungracefully shall we say and the login table may still show them logged in. Jan -----Original Message----- From: "Bill Owens" <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Wed, 5 May 2010 15:03:05 -0400 Subject: [RBASE-L] - RE: [SPAM] [RBASE-L] - Re: Determine session count of compiledRbaseapplication DOES anyone know if there is a way to limit 1 sesson per machine using V8 runtime? Thanks From: [email protected] [mailto:[email protected]] On Behalf Of Lawrence Lustig Sent: Wednesday, May 05, 2010 9:34 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: [SPAM] [RBASE-L] - Re: Determine session count of compiledRbaseapplication << I am not sure what compiler you are using but 7.6 have a checkbox labeled “allow only one instance of compiled application”. The default is unchecked but if you check it your user will not allow to open multiple instances of the application on the same machine. I am sorry to hear that Xtreme does not allow multiple instances to run on the same computer. >>>> One of the new features in the 9.0 Extreme compiler is to allow only one session. >> Manuel: I haven't seen v9 (except screenshots) but my interpretation of Jan's statement is that the 9.0 compiler offers the same feature you're seeing in the 7.6 compiler — the ability to _optionally_ limit compiled EXEs to a single instance, not that it makes it impossible to run multiple copies. If you see that option in your 7.6 compiler it means it's not entirely new in version 9, but I don't think it was in the original 7.6 compiler either, so it must have been back-ported into 7.6 as they were developing 9. I could be wrong, but that's the way I read it. -- Larry
