ACCESS LIST BOX SCROLL LOCK

[Guest]

A Scroll Lock option should be added to the 'Other' Properties Tab for List
Boxes. If this property is set to No, then the List Box should exhibit no
change in feature from the current version. If set to Yes, then the selected
item in the List Box should be vertically centered whenever it is changed.
There would be three exceptions to this feature: 1) Centering would not occur
if the selection were near the top or bottom of the list where absence of
previous or subsequent items would naturally prevent it. 2) Similar to #1,
centering would not occur if the number of items in the list were
insufficient to produce a vertical scroll bar. 3) This property would be
contingent on the Multi Select property being set to None (otherwise, this
property would be ignored).
This feature would be useful for applications where larger lists of items
are presented in a specific sort order intended to compel users to visually
compare similar items before proceeding with their final selection.
Presently, certain users stand a greater chance of making inappropriate
selections when they proceed with the first seemingly correct item they find
without scrolling the list further to more thoroughly compare the selections.
MS Office Access 2003 (11.6355.6360) SP1

 

[Stephen Lebans]

I disagree completely. You are suggesting a non standard Windows control
UI/Appearance.

With that being said, one of the things I like best is that you can
customize the Access UI to your hearts content. It would only require a
few lines of code to achieve your desired GUI.

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.

 

[Guest]

Some of us don't like "standard" Windows control UI/Appearance, if there
really is such a thing. Try to mimic any form between Access and Excel,
write the code to support it and then tell me where the "standard" lies.
Besides, Microsoft should understand this best of all - their software is
riddled with options made to appease so many different users that its
complexity alone is as much to blame for program failures as any other
contributing factor. Indeed, the code to perform this operation IS simple
and it's exactly how I presently accomplish this task. I'm merely suggesting
that Microsoft consider adding this feature not only to save db developers
the trouble of devising this type of code (we all know that the average
Office Suite user has limited knowledge of code) but as a proud addition to
other marvelous features that could also be substituted with code, like
Validation Rules/Text and Smart Tags, for example. I fail to see the breach
of standard you insinuate.

 

[Stephen Lebans]

Obviously you are not going to listen to reason or the published WIndows
GUI specs.

 

[Guest]

Loosen up, Steve-O. It's not like Moses brought the GUI specs down the
mountain. I'm adamant about this one simply because it's HIGHLY #%*@ING
PRACTICAL! You know people would use it. Geez, already :^)