Let me try to make myself clearer.

I start in form 1 (main menu) using a bit button to bring up form 2 (on
key press form).

 

This is the code bringing up the 2nd form.
EDIT USING kprvarorder 

 

The varlistview in form 2 is used to show many orders to choose from.

The code in the varlistview then needs to go back to the bit button of
form 1 so that code can bring up form 3.

 

This is the code within the varlistview EEP.

IF vControl IS NULL OR (SLEN(CTXT(.vControl))) = 0 THEN
   RETURN
ELSE
   SET VAR vRows = 1
   SET VAR vFormMode = 'EDIT'
   PROPERTY Btn_Close VISIBLE 'FALSE'
   PROPERTY Btn_Close VISIBLE 'TRUE'
--   CLEAR VAR IV%,RBTI_%,vRows,vKeyWord,vSearchString,vWhereClause, +
--   vQuotes,vPause2Message,vRows,vMany,vFormMode,vSearchWhat
--   CLOSEWINDOW
ENDIF
RETURN

 

Then the code in form 1 bit button should bring up form 3 with 

EDIT USING kayparkeditorder MDI

 

Could it be the focus is never returning to the form 1 bit button?

I have tried the suggestions given but form 2 stays up but will not let
me go to form 3.

 

From: [email protected] [mailto:[email protected]] On Behalf Of jan
johansen
Sent: Thursday, December 27, 2012 1:12 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: form stays

 

Jim,

 

When you call up a form MDI, the code immediately following the EDIT
USING continues.

It does not wait for any action inside the called form.

 

Jan

         

        -----Original Message-----
        From: "Jim Belisle" <[email protected]>
        To: [email protected] (RBASE-L Mailing List)
        Date: Thu, 27 Dec 2012 11:58:38 -0600
        Subject: [RBASE-L] - Re: form stays

        Albert and mike,
        
        I tried that as well
        
        This is the code bringing up the 2nd form.
        EDIT USING kayparkeditorder AS MDI
        
        I still have to escape from the Onkeypress form (not associated
with any
        table) to see the new form.
        
        This is the code when I double click on the varlisview form.
        I commented the clear var and closewindow code for testing.
        
        IF vControl IS NULL OR (SLEN(CTXT(.vControl))) = 0 THEN
           RETURN
        ELSE
           SET VAR vRows = 1
           SET VAR vFormMode = 'EDIT'
           PROPERTY Btn_Close VISIBLE 'FALSE'
           PROPERTY Btn_Close VISIBLE 'TRUE'
        --   CLEAR VAR
IV%,RBTI_%,vRows,vKeyWord,vSearchString,vWhereClause, +
        --   vQuotes,vPause2Message,vRows,vMany,vFormMode,vSearchWhat
        --   CLOSEWINDOW
        ENDIF
        RETURN
        
        
        -----Original Message-----
        From: [email protected] [mailto:[email protected]] On Behalf Of
Albert
        Berry
        Sent: Thursday, December 27, 2012 11:46 AM
        To: RBASE-L Mailing List
        Subject: [RBASE-L] - Re: form stays
        
        Call the form MDI.
        Albert
        
        On 27/12/2012 10:38 AM, Jim Belisle wrote:
        >  
        >
        > I have a on key press form with a varlistview box for bringing
up
        > orders.
        >
        > This works fine to bring up the order on a double click and
the on key
        
        > press form then closes.
        >
        >  
        >
        > One of my clients has this request:
        >
        > He wants the on key press form to stay in the background in
case he
        > wants to go back to look at another order for the same
customer. He
        > does not want to have to click to bring up the form, then type
in the
        > same customer code each time.
        >
        >  
        >
        > I have changed the code in the varlistview to eliminate the
        > closewindow line.
        >
        > If I do that the form stays up but the next form does not come
up.
        >
        >  
        >
        > Any suggestions?
        >
        >  
        >
        > James Belisle
        >
        >  
        >
        > Making Information Systems People Friendly Since 1990
        >
        >  
        >
        >  
        >
        >
        >
        >
        > -----
        > No virus found in this message.
        > Checked by AVG - www.avg.com
        > Version: 2013.0.2805 / Virus Database: 2637/5988 - Release
Date:
        > 12/26/12
        >
        
         

 

Reply via email to