Yes! Thank you! Been banging my head against the "how-do-I-conditionally-call-up-Form-X" wall for two days. Ouch. Ah, relief.
Bruce Chitiea 909.238.9012 cell > On Oct 3, 2013, at 7:20, "MikeB" <[email protected]> wrote: > > I mentioned the Switch/Endsw approach simply because it gives you some > flexibility (testing for other conditions) and can still include the Skip > command within the Switch/Endsw. > > > For example if a certain condition isn't met and you want to stay in that > field or even open another form, etc. > > > >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On Behalf Of >> Richardson, Jeff >> Sent: Thursday, October 03, 2013 10:05 AM >> To: RBASE-L Mailing List >> Subject: [RBASE-L] - RE: Tab Property? >> >> After some adjustments, the SKIP command is now serving me well. Thank >> you all for the input. >> >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On Behalf Of MikeB >> Sent: Wednesday, October 2, 2013 3:56 PM >> To: RBASE-L Mailing List >> Subject: [RBASE-L] - RE: Tab Property? >> >> You won't have to define a variable if each of your fields has a >> CompID. >> >> You can use an eep on your speed button and use a switch/endsw with >> each CASE statement tied to the global variable RBTI_FORM_COMPID (which >> is the compID of the most recent control that has a compID) and then >> with each CASE statement you could use the PROPERTY compID SET_FOCUS >> 'true' statement to advance to the next edit field. >> >> >> Having said ALL that, "SKIP 1" advances to the next field on my machine >> as Javier suggests. >> >> >> >> >>> -----Original Message----- >>> From: [email protected] [mailto:[email protected]] On Behalf Of >>> Richardson, Jeff >>> Sent: Wednesday, October 02, 2013 3:40 PM >>> To: RBASE-L Mailing List >>> Subject: [RBASE-L] - RE: Tab Property? >>> >>> Thank you for the hints... Incidentally, the SKIP command had no >>> effect in my application, but I never knew it existed, so I'm glad it >>> was mentioned. >>> >>> I am thinking now that my solution will involve a variation of the >>> SET_FOCUS, but since I might be pressing my speed button from any >>> number of DB edit fields and the next field is dynamic, I will need >> to >>> define a variable when I enter a DB edit field that defines the next >>> field. So my command then is PROPERTY &vnextfield set_focus 'true' >>> >>> >>> >>> -----Original Message----- >>> From: [email protected] [mailto:[email protected]] On Behalf Of >> Javier >>> Valencia >>> Sent: Wednesday, October 2, 2013 3:23 PM >>> To: RBASE-L Mailing List >>> Subject: [RBASE-L] - RE: Tab Property? >>> >>> Have you tried the SKIP command? >>> Also, if you know the next field and it has a component ID, you can >>> use: >>> PROPERTY vComponentID SETFOCUS 'TRUE' >>> >>> Javier, >>> >>> Javier Valencia, PE >>> O: 913-829-0888 >>> H: 913-397-9605 >>> C: 913-915-3137 >>> -----Original Message----- >>> From: [email protected] [mailto:[email protected]] On Behalf Of >>> Richardson, Jeff >>> Sent: Wednesday, October 02, 2013 2:01 PM >>> To: RBASE-L Mailing List >>> Subject: [RBASE-L] - Tab Property? >>> >>> Hello. Does anyone know a Form PROPERTY command that will >>> automatically TAB to the next field/form control in the Tab Order >>> list? For example, I want to be focused in one database edit field >>> and press a speed button that performs a series of operations, and >>> then have it advance the focus to the next database edit field down >>> the line without the user actually needing to press the tab key on >> the >>> keyboard. Thanks for any thoughts! > >
