Form Jumps On Tab Click (1 Viewer)

Friday · Feb 25, 2004

Searched for this and couldn't find the right thread (it's probably out there somewhere). Form with 2 tabbed controls on it. Each tab has a subform on it. When the user clicks on the first tab, the entire form jumps down to the first tab stop (field) on the subform1, hiding the top 1/4 of the form. Now the user has to scroll up to find the tabs so the second tab can be clicked. And, again, it jumps down to the first tab stop on the subform2. Can this be avoided?

Bob_Langley · Apr 1, 2004

Friday said:
Searched for this and couldn't find the right thread (it's probably out there somewhere). Form with 2 tabbed controls on it. Each tab has a subform on it. When the user clicks on the first tab, the entire form jumps down to the first tab stop (field) on the subform1, hiding the top 1/4 of the form. Now the user has to scroll up to find the tabs so the second tab can be clicked. And, again, it jumps down to the first tab stop on the subform2. Can this be avoided?

I have a similar problem when the Form opens. The Form header is visible as is most of the form but the tab captions are not. The user has to scroll up by about 1" to reveal the tabs.

JohnEC · Apr 5, 2004

Similar situation III

Bob_Langley said:
I have a similar problem when the Form opens. The Form header is visible as is most of the form but the tab captions are not. The user has to scroll up by about 1" to reveal the tabs.

Me too. Any guesses?

Pat Hartman · Apr 5, 2004

You need to resize the controls that hold the subforms so they're bigger.

JohnEC · Apr 6, 2004

Resizing controls doesn't do the trick

Pat Hartman said:
You need to resize the controls that hold the subforms so they're bigger.

Resizing controls doesn't do the trick

daisyage · Jul 16, 2004

count me in!

i am having the same problem. i created a form with 7 pages. 5 of the pages have subforms. when i click on a page with a subform, the main form jumps down and hides the page controls. if anyone has done this troubleshooting before, please share the joy! i've tried 'GotoControl' and 'GotoPage' it works on some pages and not others.
thanks for any help!!!

WindSailor · Jul 16, 2004

The only time I have seen this happen is when the mainform and/or subforms have been actually designed on a display setting, and then viewed on a different display setting other than what they were designed for, or... if every thing is sized correctly go back into design mode and move the bottom dimensions of your form and/or subform(s) up or down to correct this.
Thats about all I know on this subject. Hope it helps.

daisyage · Jul 20, 2004

one solution

i used the MoveSize macro for the subform and form and set it to move down on enter. may not be the best solution, but it worked!

Pat Hartman · Jul 20, 2004

Sizing the subform and tab control properly would also have worked

green · Jun 17, 2011

Pat - I have tried your recommendation. I created a test form and added it as a subform to one of my tabs and it works correctly. But I can't figure out how to re-size either my original subform or tab control so that they play nice together. Thanks.

missinglinq · Jun 17, 2011

This problem is usually the result of two things, the first being that the Form and/or Tabbed Control are/is too long to be completely displayed without scrolling. As Pat said, they need to be resized so that scrolling them is never needed.

The second part of the problem is usually what Control on the Tabbed Page receives Focus when the Tabbed Page is first clicked on. The Control first receiving Focus is low enough that the Form has to be scrolled to display it. This can be remedied by forcing Focus to a Control at the top of the Tabbed Page, but if the Form is sized so as to never need scrolling, the problem wouldn't exist.

Preventing the need to require the user to scroll a Form in order to access all Controls is one of the two reasons for having Tabbed Controls. The second reason is to allow for the logical grouping of Controls within the Form.

Linq ;0)>

green · Jun 17, 2011

Thanks, Linq! I didn't make the connection between the subform being long and the auto-scroll. In my project the best arrangment is to leave the subform long with scrolling. (I am using tabs to group data by applicable subject matter.) I have verified my field tab order is correct. How can I tell how which contol is otherwise getting focus first? Secondly, do I use an On Open function to assign focus to the control I want instead of the system assigned focus?

green · Jun 23, 2011

I was able to resolve the issue by resizing the tab control to fit within the screen size and limit the subform to the size of the tab contol. Now the subform has a scroll bar but the subform doesn't auto-scroll.

missinglinq · Jun 24, 2011

Glad you got it fixed, Idaho! Scrolling a Subform is perfectly acceptable, but having to scroll the Main Form, in order to view all of the Controls, is considered, by most experienced developers, to be one of the most user-unfriendly things you can do!
BTW, using Tabbed Controls to logically group data is a great approach! So many people, both newbies and some not-so-newbies, only think of using them when Subforms are needed. And the great thing, of course, when putting Controls directly on a Tabbed Page, is that it's referenced the same as it would be if simply added directly on the Form's main detail area.

Linq ;0)>

Clicky · Jul 12, 2018

I've been scouring the internet for a solution to this and realized there are a number of ways of fixing. But even if you resize the subforms/tab forms to ensure everything fits on one page, it may look fine on a regular computer screen, but the window may still jump down when it's a laptop screen.

This may be posted somewhere, but I figured out a solution that worked for me.
- I created buttons over each tab (no caption and no background color so they look hidden).
- In the OnClick event for those buttons, I set the focus to the tabbed subform and then set the focus to a control at the top of the main form.
- And then it worked! When clicking on the button over the tab, the focus is set on the tabbed subform, and then the main form is forced to scroll back up to the top to set its focus on a field near the top.
- I then noticed there was a bit of flickering when the form would set its focus on one field and then quickly to another. I found on the forums somewhere about the echo function and that made it flicker less. Below is the code that worked for my situation.

'These are for invisible buttons on each tab to ensure the screen won't jump down. Otherwise, on laptop/small screens, clicking the tab may make the screen jump down, hiding the top portion of the form
Private Sub btnTabA_Click()
Application.Echo False
Me.TabAForm.SetFocus
Me.FieldatTopofMainForm.SetFocus
Application.Echo True
End Sub

missinglinq · Jul 13, 2018

Clicky said:
...even if you resize the subforms/tab forms to ensure everything fits on one page, it may look fine on a regular computer screen, but the window may still jump down when it's a laptop screen...

FYI...This has nothing to do with whether you're on a 'regular computer' or on a 'laptop'...i.e. whether you're on a large screen or a small screen...the behavior is caused by different screen resolutions on the two machines!

Because of this, the same problem could crop up between two or more 'regular' computers, if their screen resolutions were different...a problem often encountered in corporate environments.

There are hacks out there that address the problem of distributing an app among PCs of different screen resolutions.

Linq ;0)>

gemma-the-husky · Jul 18, 2018

Similar thoughts to missingling above

you can set controls as non tab-stop, and set the tab order.

However, if you tab to a control off the page, then I can't see how you can prevent the form being forced to redraw.

Is it possible to redesign the from so that the controls are shown in a different way - maybe group associated controls on a tabbed control (different from pressing the "tabs" key) - so that the whole form can be displayed on the screen.

With regard to the display resolution, I desgin for a standard resolution - say 1024 x 768, and at startup, I check the resolution and warn users if their resolution is lower than this.

Although you can repostion and resize controls to fit any screen res, it's a big job, and it may not be acceptable for some forms if users use something like 800x600

If they do use a smaller res, then you need to ensure you include scroll bars where appropriate.

api calls to get the screen res are
GetSystemMetrics(SM_CXSCREEN)
GetSystemMetrics(SM_CYSCREEN)

Form Jumps On Tab Click (1 Viewer)

Friday

Registered User.

Bob_Langley

Guest

JohnEC

Guest

Pat Hartman

Super Moderator

JohnEC

Guest

daisyage

Guest

WindSailor

Registered User.

daisyage

Guest

Pat Hartman

Super Moderator

green

Registered User

missinglinq

AWF VIP

green

Registered User

green

Registered User

missinglinq

AWF VIP

Clicky

New member

missinglinq

AWF VIP

gemma-the-husky

Super Moderator

Similar threads

Users who are viewing this thread