[RBG7-L] - RE: Property TABORDER Question

[David M. Blocker]

Sami, Aleksey and Charlie   Thanks for your help!  The combination of starting with 0 instead of 1, counting BACKWARDS and the PROPERTY .. SET_FOCUS 'TRUE' commands did the trick!   David Blocker [EMAIL PROTECTED] 781-784-1919 Fax: 781-784-1860 Cell: 339-206-0261 ----- Original Message ----- From: Aleksey Chuyasov To: RBG7-L Mailing List Sent: Monday, June 28, 2004 5:39 PM Subject: [RBG7-L] - RE: Property TABORDER Question David,   TabOrder property starts with 0, and also I recommend you to number components in reverse sequence.   For example:   you have DBEdit1, DBEdit2, Button1, Button2   Your original taborder is:   DBEdit1 -> DBEdit2-> Button1 -> Button2   and you want to have the following sequence:   Button1 -> DBEdit2 -> Button2 -> DBEdit1   your sequence must be:   PROPERTY DBEDIT1 TABORDER 3 PROPERTY BUTTON2 TABORDER 2 PROPERTY DBEDIT2 TABORDER 1 PROPERTY BUTTON1 TABORDER 0 PROPERTY BUTTON1 SET_FOCUS TRUE   This example works fine if your components are located on a form, not in "containers" (Such as Panels or GroupBoxes).   If your components are located in containers, you need to assign the TabOrder for the containers too.   Example:   You have   Form |-Panel1 |- DBEdit1      |        |- Button1      |              |-Panel2 |- DBEdit2      |      |-Button2   DBEdit1 located on Panel1 Button1 located on Panel1 DBEdit2 located on Panel2 Button2 located on a Form.   and for example you want to make the following Tab Sequence:   DBEdit2 -> Button1 -> DBEdit1-> Button2   --Changing TabOrder property for last component in sequence PROPERTY Button2 TABORDER 2 --Changing TabOrder property for Panel1 in sequence --Because DBEdit1 and Button1 located on Panel1  PROPERTY PANEL1 TABORDER 1 --Now change the TabOrder for child components of Panel: --Last must be a DBEdit1 and first must be Button1 --This will change the TabOrder sequence inside container PROPERTY DBEdit1 TABORDER 1 PROPERTY Button1 TABORDER 0 --Changing TabOrder property for Panel2 in sequence --To make sure that the Panel2 is the first component in sequence  PROPERTY PANEL2 TABORDER 0 PROPERTY DBEdit2 SET_FOCUS TRUE RETURN   Hope that helps.   Best, Aleksey Chuyasov.           ----- Original Message ----- From: "Sami Aaron" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> Sent: Monday, June 28, 2004 5:13 PM Subject: [RBG7-L] - RE: Property TABORDER Question > David - > > I'm going to take a stab at this and suggest that the tab order numbering > starts with 0 (zero) and not one ... > > Sami > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of David M. > > Blocker > > Sent: Monday, June 28, 2004 3:48 PM > > To: RBG7-L Mailing List > > Subject: [RBG7-L] - Property TABORDER Question > > > > > > Hi friends > > > > This scenario is under Release 75. > > > > I have a very simple form with 1 Static text control, ID > > ‘TitleAccount’, and > > 2 DBEDIT controls, ACCT AND ACNM., and 2 other static text controls as > > labels for the 2 DBEDIT fields. > > > > At the bottom of the form are a line of Push button controls for each > > possible action EVER with that form: > > > > First > > Previous > > Next > > Last > > Add and Continue > > Add and Exit > > Discard Changes > > Delete and Continue > > Save > > Save and Exit > > Exit (actually a Bit Button control) > > > > Each has a component ID composed of “But” plus the text on the button with > > no spaces (ButFirst, ButPrevious, ButAddandContinue, etc.) > > > > The default tab order of the fields under Layout / Change Tab order is as > > shown above: the 2 dbedit controls, then the buttons. > > > > On after start of the form, I have an EEP which controls which buttons / > > fields are activated depending on whether the form is used for > > adding data, > > editing data, or viewing data.  With one minor exception, it works GREAT. > > > > Here is the section of code for the VIEWING option: > > > >     PROPERTY TitleAcct CAPTION 'ACCOUNTS VIEWING' (changes the form title) > >     PROPERTY ACCT TABSTOP 'FALSE' > >     PROPERTY ACNM TABSTOP 'FALSE' > >     PROPERTY ACCT ENABLED FALSE > >     PROPERTY ACNM ENABLED FALSE > >     PROPERTY ButAddAndContinue ENABLED > > FALSE > >     PROPERTY ButAddAndExit ENABLED FALSE > >     PROPERTY ButDiscardChanges ENABLED FALSE > >     PROPERTY ButSave ENABLED FALSE > >     PROPERTY ButSaveAndExit ENABLED FALSE > >     PROPERTY ButDeleteAndContinue ENABLED > > FALSE > >     PROPERTY ButNext TABORDER '1' > >     PROPERTY ButLast TABORDER '2' > >     PROPERTY ButFirst TABORDER '3' > >     PROPERTY ButPrevious TABORDER '4' > >     PROPERTY ButExit TABORDER '5' > > > > The issue is TABBING.   What I WANT is that the form will come up with the > > NEXT button highlighted, so that the user could just press > > [Enter] and would > > select NEXT.  What HAPPENS is that when the form comes up, I can’t tell > > where the tab is. Pressing [Enter] does NOTHING. If I press [Tab] > > ONCE, then > > it highlights the NEXT button and from then on, all works OK.  The tab is > > order is correct, tabbing never lands where I don’t want it.  It > > just doesn’ > > t START with the TABORDER ‘1’ highlighted.  Is there another property I’m > > missing?  Why doesn’t TABORDER ‘1’ automatically mean the cursor RESTS on > > that control when you start up the form? > > > > The TABSTOP controls were added in an attempt to solve the > > problem, but they > > have no affect at all, whether set to TRUE or FALSE, and I suspect that's > > because the same controls have ENABLED set to FALSE. > > > > Any ideas? > > > > David Blocker > > [EMAIL PROTECTED] > > 781-784-1919 > > Fax: 781-784-1860 > > Cell: 339-206-0261 > > > > > > > > >