I have a form contains a tab control. This tab control has 7 tabs ( 7 pages). Each page contains a subform.
When I am in the first page and hit the last control of this page. I use set focus to move to next tab (next page) first field.
here is the code...
Forms!frmentry.TabCtlEntry.Value = 1
Forms!frmentry.sfmREC.SetFocus
Forms!frmentry.sfmREC.Form!comReview.SetFocus

When it runs, it moves to next tab (next page) but not the field comReview. It sets focus to the field that follows comReview.
I tried to use different ways to set the focus for each page when the subform is load, or is open, or is current. It doesn't work.
Please help...
Thanks
MYC

Is there any event procedure code in the subform that might be taking the focus away from the control you wanted?

In the last control of the first subform (first page) I used the keydown event to check if it is tab key or return key entered. If it is, then set the focus to next tab (2nd page). I don't see any event after this.

I am wondering then if it might be a timing issue. Try putting a call to DoEvents before setting focus to comReview and see if that makes a difference.

Mike

I thought about the timing too so I added a line of moving a field in. It doesn't help. what kind of DoEvents I can use?
Mindy

This would give the application time to finish other things before setting focus to the control.

Not sure if it will work, just something to try. I have sometimes found it worked in certain cases.

The alternative approach you could try would be a bit more of a change... you could move the code to the subform itself and expose it as a public method. But we'll hold off on it for now until we know if DoEvents did the trick reliably.

Mike

I tried. DoEvents doesn't help. I am not sure how to do what you suggested -- move code to subform then expose it as public. Could you please explain more???
Thanks.

In the subform itself, you would use code somethig like this:



Then in the main form:



It feels like a bit of a hack, I know, but sometimes this kind of thing can work. In fact, if you get comfortable creating methods in subforms it can actually help you remove a lot of headache in complex applications. Rather than have subform-specific code in the parent form, put it into the subform and merely call it from the parent form.

Mike

I am not sure how this work. Originally I put the SetFocus in the last control of subform. Now, I need to put in Main form. Where is it in main form? how can this code be called?

What I'd try is in each Form that your Subforms are based on, in their Form_Current events, set the Focus to the appropriate Control for that Form.

BTW, DoEvents is always a good thing to try, when possible timing problems raise their ugly heads! Only takes a few seconds to try, and does now harm, even if it doesn't work!

Linq ;0)>

I also tried the way you suggested but it didn't work. I really couldn't figure out. It just skipped to next field.

what control Event you use in switching Tab. If it is in KeyDown or KeyUp you can use KeyCode = 0 inside this procedure.

I use keydown to check if it is tab key or return key. I am not sure what do you mean to use keycode=0. Please explain. thanks.

when you used the keydown event to inspect the key just pressed, in this case the TAB or RETURN, the TAB/RETURN is still in the KEYBOARD buffer.

You need to clear this buffer first by issuing KeyCode = 0.

So on your code, TAB/RETURN is inspected.
If found any of these keys it switches Page, but since TAB/RETURN keycode is still in the keyboard buffer, it will TAB/RETURN from the first control.

In pseudocode:




This post has been edited by arnelgp: Apr 13 2012, 02:31 AM

Thank you very much. It works. I find a way to go around it. But your way is the best one.