Thanks, but I would rather be able to determine the session count. 

It is not outside logic that certain users might need to have two sessions 

open.  If I can obtain a session count, I can then set by user, the number 

of allowed sessions and enforce it programatically. 



-Bob 



----- Original Message ----- 
From: "jan johansen" <[email protected]> 
To: "RBASE-L Mailing List" <[email protected]> 
Sent: Thursday, April 29, 2010 10:41:39 AM GMT -06:00 US/Canada Central 
Subject: [RBASE-L] - Re: Determine session count of compiled Rbaseapplication 



Bob, 

One of the new features in the 9.0 Extreme compiler 
is to allow only one session. 

I encourage you to explore that option. 

Jan Johansen 
  
  

-----Original Message----- 
From: [email protected] 
To: [email protected] (RBASE-L Mailing List) 
Date: Thu, 29 Apr 2010 15:35:09 +0000 (UTC) 
Subject: [RBASE-L] - Determine session count of compiled Rbase application 



This may have been discussed before, so my apologies if I missed it. 

I have several users that run on Terminal server via touch screen tablet 
thin clients.  When they start up a compiled Rbase app, they double tap the 
touch screen  on the app icon.  Touch screens are not always the best 
input for double tapping and often, they do not get the program started the 
first try. (These are portable tablets mounted on fork lifts and do not have 
mouse, 
keyboards nor stylus.   Totally touch screen as drivers cannot be fooling 
around 
with mice and stylus) 

As impatient users often are, if they do not see something show immediately, 
they start double, triple, quadruple tapping the screen.   Then they wind up 
with 4-5 sessions running.  (Yes, I have a SHOW LOADING dialog window, but they 
often do not wait for that to show) 

So I want to have a process in my startup routine to check to see if any 
existing sessions of the compiled app is running.   I.E. if the app is named 
"CompiledApp.exe" how can I check from within Rbase if that exe is already 
running?   If it is, I will have the startup routine display a message as such 
and 
then shut down the second session.   I guess I need to check the number of 
sessions of "CompiledApp.exe".   If only 1 is found then all is OK, if the 
count 
is 2 then shut down the session. 

Thanks, 
-Bob 
 

Reply via email to