TM - YTH.
Your response supports the idea of a "wiki-RB Help".  I didn't realize it was a db setting, that wasn't explicitly stated in the Help.  But now reading through the help, things like  "RESET - Clears out the ON CONNECT/PACK command recorded in the database" makes sense.

Is there a command to SHOW CONNECT?  I read through the results of R>SHOW and didn't see anything relating to CONNECT.

I did the RUN SELECT .. thing, but still get a "No Database Connected", which is strange because it has to be connected to read the IntCmd table.
This is the code called by RUN SELECT:

--set trace on
PROPERTY APPLICATION TITLE  'Ryan Menu'
EDIT USING mainmenu
set trace off
RETURN
 

The PROPERTY APPLICATION TITLE command executes, so I know the RUN SEL is executing.
MainMenu has no DISCONNECTs in OBS EEP or OAS EEP.  It is a variable form (no table).

Any ideas?

Thanks,
Doug


MikeB wrote:
First, treat the "ON CONNECT" as a setting because you only have to do it once.

You would do it from the command line as it becomes part of the DB settings 
that are preserved across sessions.

One of the hidden nuggets of this ON CONNECT business is that the following 
works like a charm so you don't have any of those little files running around 
on disk:

on connect run select cmddata from intcmd wher cmdname = 'startup' save

so you can put the contents of your RBMenu.dat in a VarChar data in a table and 
run it from there.

Everything described in the HELP file works..

HTH



----- Original Message ----- 
From: "Doug Hamilton" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Thursday, October 30, 2008 11:43 AM
Subject: [RBASE-L] - RE: Mult-iusers, Multi-sessions, Mult-iPCs ON CONNECT


  
This thread got me thinking about using the ON CONNECT command to tailor (pun 
intended, Frank) multiple sessions.
My first RB session I'd like to bring up the app's main menu for testing, 
subsequent session(s) would open into RB Explorer (to fix all the errors).

So my RBase.DAT is:
PROPERTY APPLICATION TITLE 'RB Devel'
On first connect run RBMenu.dat
CONNECT ThreePty
RETURN

RBMenu.DAT is:
PROPERTY APPLICATION TITLE  'RB Menu'
CONNECT ThreePty
EDIT USING mainmenu
RETURN

But I get errors when RBMenu.DAT runs:
"Illegal command in Entry/Exit Procedure."

So I took out the redundant CONNECT ThreePty and get "No Database Connected. 
Please Retry After Connecting."

Can anyone give me more insight into the ON CONNECT command?

Addressing the original issue of multiple sessions, could ON FIRST CONNECT 
run your RB session, subsequent attempts would open an external form that 
says Rbase is already running?

Thanks,
Doug

Frank Taylor wrote:

 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.



 <!--[if !supportLists]-->n  <!--[endif]-->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 **
 _______________________________________________________________________


    



  

Reply via email to