Can ListBox be pre-loaded for better scrolling?

[deko]

I have an Access 2003 mdb with a Main Form that has a ListBox with a long
list of items. The problem is the scroll bar on the ListBox does not scroll
all the way to the end unless you first scroll half way, then let up the
left mouse button, and then continue to scroll to the end of the list. But
once you've scrolled the entire list once, the scroll bar works fine.

The Main Form gets requeried at times due to different events which puts the
ListBox scroll bar behavior back in the half-way mode again. Is there a way
to pre-load the ListBox so I can avoid this annoying scroll bar behavior?

Thanks in advance.

[Rick Brandt]

deko wrote:

I have an Access 2003 mdb with a Main Form that has a ListBox with a
long list of items. The problem is the scroll bar on the ListBox
does not scroll all the way to the end unless you first scroll half
way, then let up the left mouse button, and then continue to scroll
to the end of the list. But once you've scrolled the entire list
once, the scroll bar works fine.

The Main Form gets requeried at times due to different events which
puts the ListBox scroll bar behavior back in the half-way mode again.
Is there a way to pre-load the ListBox so I can avoid this annoying
scroll bar behavior?

Thanks in advance.

I think if you add a line of code that retrieves the ListCount that it forces
the ListBox to retrieve all of its rows. This will of course introduce a delay
while that is occurring. You might simply be replacing one problem with
another.

It is usually considered a *good* thing that Access ComboBoxes and ListBoxes do
not retrieve all of their rows when first displayed. Why retrieve data that
might not be needed? For someone reviewing existing entries they might not even
use the items in the list at all and yet they will still pay the performance
penalty for having all of that data retrieved.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[deko]

> I think if you add a line of code that retrieves the ListCount that it
forces

the ListBox to retrieve all of its rows. This will of course introduce a delay while that is occurring. You might simply be replacing one problem with
another.

Thanks for the reply. Can you give me an example of how I would do this? I
understand there may be latency cost in doing this, but it's a price I'm
willing to pay.

[Rick Brandt]

deko wrote:

I think if you add a line of code that retrieves the ListCount that
it forces the ListBox to retrieve all of its rows. This will of
course introduce a delay while that is occurring. You might simply
be replacing one problem with another.

Thanks for the reply. Can you give me an example of how I would do
this? I understand there may be latency cost in doing this, but it's
a price I'm willing to pay.

Just set a variable to the ListCount property.

Dim MyVariable as Long

MyVariable = Me.ListBox.ListCount

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[deko]

> Just set a variable to the ListCount property.

Dim MyVariable as Long

MyVariable = Me.ListBox.ListCount

That works great!! Thanks!! The convenience of being able to immediately
scroll all records is well worth whatever latency I'm paying. Thanks
again - this is a very nice improvement!