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 > > > >
