Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 210
  • Last Modified:

Listbox Memory Question

What are the biggest differences between a listbox and a virtual listbox?   The speed in which information is loaded?  The amount of memory taken up?  Where that memory is located?  I understand how each is created I was just wondering about speed and memory usage comparison.

I realize this is probably a no-brainer, I just thought I would come to the "source of great information" for a quick and highly reliable answer.  :-)

1 Solution
Wim ten BrinkCommented:
Virtual listbox are virtually unlimited in size because they just retrieve the information when you need them. A normal listview demands that you fill it completely with data before it can be shown.
Imagine that you have 100.000 items, but only 30 of them would be visible. A virtual listview would just retrieve the 30 values that it needs to display. A normal listview needs to be filled with all those records first before you can use it. Filling it up costs a lot of time. And of course it would also eat up a lot of memory...

Virtual listviews are especially useful with queries that return a huge amount of data. The data will be stored in the recordset somewhere and the virtual listview will just maneuver through this recordset. A normal listview needs to have a copy of all this data internally before it can start displaying, thus you'd double the amount of required memory. Besides, making that copy consumes a lot of time.
alexiatAuthor Commented:
Thanks.  Exactly what I wanted to know.

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now