Entire Form does not display, can't scroll

[stevehoyle]

I created a Form, works fine. I ported to production. Some users have XP, some Win7. Some of the displays are set with different resolution. Some users couldn't see the entire form. If I changed to a higher resolution, then they could. But some users desire the lower resolution. The problem is that the scroll bar on the bottom of the Form has no effect. The right side of the form is clipped, when the scroll bar is slid to the right nothing happens. If I click at the rightmost position on the scroll bar, it doesn't slide. How do I fix this? How do I code my forms to work for every one? Do I have to design it with the lowest resolution that is used in the environment?
Thanks,
Steve

[June7]

Users have to use the application scroll bars as well as the form scroll bars.

You can either resize and reconfigure the forms to accommodate the lowest resolution any user will set or they have to use scroll bars.

[stevehoyle]

OK, thanks. I obviously don't want scroll bars. I redesigned everything to work with 1024x768, I'm assuming everyone could at least set to that as a minimum. Everything looked good. I migrated to the work test environment. Display is still messed up. I no longer have to scroll, but fields I had defined (column widths, labels, etc.) are now truncated. It makes no difference when I change resolution, it gets bigger or smaller, but always truncated in the exact same manner. On the property sheet I change the width to a few more inches, changed Auto Resize from No to Yes, changed Fit to Screen from No to yes, nothing changes. Everythig remains truncated in the exact same way. I go back to my initial development environment (it is a laptop), everything appears perfect. I'm very confused (and frustrated, and disappointed, and tired - for good measure.)

[June7]

What happens on the laptop if you set that resolution?
Sorry, not an issue I ever dealt with so no more ideas how to fix.

[stevehoyle]

I did code again to 1024x768. I moved again to production. It was better but there were still differences. Some of my control boxes were slightly higher or lower in the header. I corrected, moved back to the laptop and they were off again. Makes no sense, 1024x768 defines the space, the relationship between pixels doesn't change. They are both Access 2007, one is home and student and one is professional. But I don't think that should do it. One more problem I have, I can't see how to change navigation sequences. If I tab across a row, in the header or detail, it doesn't always go to next cell. How do I define the sequence? Also, the down arrow goes to lower row on my queries, but to the adjacent cell in my forms. I want it to go down. Thanks

[June7]

Again, not issues I have dealt with. Maybe the student version is an issue.

The cursor keys will move cursor according to the TabStop value set for the controls when form in Continuous or Single view.

[stevehoyle]

One more problem I have - I can't see how to change navigation sequences. If I tab across a row, in the header or detail, it doesn't always go to next cell. How do I define the sequence? Also, the down arrow goes to lower row on my queries, but to the adjacent cell in my forms. I want it to go down. Also, I have a date field with a date picker. The field is mm/dd/yy. If I select from the date picker the field shows 2013 only, when I tab out then it shows mm/dd/yy. How do I change the date picker to retrieve in the same format? Thanks

[June7]

The TabStop property of each data control determines the navigation order on Continuous and Single view forms.

I don't use date picker. I usually setup date textboxes with input mask. Again, cannot replicate the issue.

[stevehoyle]

[QUOTE=June7;193738]The TabStop property of each data control determines the navigation order on Continuous and Single view forms.

TabStop selections are either yes or no. Mine are all yes. How is this controlling navigation sequence?

[stevehoyle]

Found it. It is called Tab Order

[June7]

Sorry, crossed wires when typing and mixed up TabStop and TabOrder properties.

[stevehoyle]

That's OK, I really appreciate your help. My only remaing problem is navigation with the down arrow key. If on a Query the down arrow goes to the field below on the next record. If on a form it goes to the adjacent column on the same record. How do I get the down arrow to act the same on the form as the query? On the form CTRL PgDn does this action, but I want the down arrow to do it. Thanks

[June7]

The form is in Datasheet mode? I can't replicate what you describe. The arrow keys work as expected.

I thought cursor movement might be influenced by application settings. Click Office Logo > Access Options > Advanced > Editing > Arrow Key behavior, that does change behavior of left/right arrows but not up/down.

[DavidT]

Perhaps it is the office ribbon bar that is offsetting your form size. I had the issue where I was configuring form control layout in the Form_Load event. Code did not account for the space taken by the office ribbon bar. Just a thought.

[stevehoyle]

Thanks David. I don't have the ribbon bar, I have a switchboard with no navigation pane and no toolbars.