Load a huge data into dropdown list

[aspfun via DotNetMonster.com]

I Microsoft Access, using ODBC to load huge record (Claim number, about 300,
000 rows) to combo box is fast.
I try to load the same amount of claim number into ASP.NET dropdown list but
program frozen.
How to load it?

--
Message posted via DotNetMonster.com
http://www.dotnetmonster.com/Uwe/Forums.aspx/asp-net/200911/1

[Mr. Arnold]

aspfun via DotNetMonster.com wrote:
> I Microsoft Access, using ODBC to load huge record (Claim number, about 300,
> 000 rows) to combo box is fast.
> I try to load the same amount of claim number into ASP.NET dropdown list but
> program frozen.
> How to load it?
>

You don't load 300,000 rows into a dropdown list. You don't even load
that amount into a Windows form combo box either.

What user would want to scroll down 299,999 entries to get to the
300,000 one or scroll up and down any amount of entries in that situation?

You use a listview control giving the user the ability to load subsets
out of 300,000, like 150 at a time using some kind of alphabetical or
numerical sequence they would enter to load the listview at the start
sequence given to load from the database table.

[Patrice]

In addition to Mr. Arnold response it might have worked for you because in a
windows application, a user is able to type and be directed to the
corresponding entry (it's very likely they just typed what they needed to
narrow down the search).

On the other hand, an HTML select tag just uses the first key pressed to
locate the first entry that match this character. On the second key, it will
locate other entries beginning by this other character, you'll have to press
the same key twice to be on entry #2 that begins with this same character
etc...

It makes selecting by typing in a huge list worse than in a windows
application.

--
Patrice

"aspfun via DotNetMonster.com" <u53138@uwe> a �crit dans le message de
groupe de discussion : 9edc538acde26@uwe...

[bruce barker]

in access the list is populated as you scroll thru it, in a web app, the
the list is built and sent to the browser.

you should either switch to a paging grid, or switch to a "suggests"
ajax control. see the ajax control toolkit or jQuery plugins

-- bruce (sqlwork.com)

[CSharpner]

It's probably not frozen. It's probably spending tons of time
downloading to the browser and rendering the HTML. Do *NOT* do this.
You need some sort of a filter built into your UI. There's no good
reason to dump 300K rows onto the user.

http://csharpner.blogspot.com

[Paul Shapiro]

The last I knew an Access combo box was limited to 64,000 rows, which is
still too many to be worth displaying. The point of a combo box is to help
the user, but that large a data list doesn't perform well enough to be
helpful. I would either let the user type the claim number into a textbox,
or use a combo box which only retrieves the row list after enough characters
have been typed to limit it to a reasonable size list. Telerik components,
for example, include a combobox which supports incremental data retrieval
and I'm sure plenty of others can be found if you don't want to write all
the code yourself.

"CSharpner" <csha...@gmail.com> wrote in message
news:99cd92bf-7b99-4a89...@j9g2000vbp.googlegroups.com...

[Alexey Smirnov]

On Nov 12, 12:42 am, "Paul Shapiro" <p...@hideme.broadwayData.com>
wrote:

> The last I knew an Access combo box was limited to 64,000 rows, which is
> still too many to be worth displaying. The point of a combo box is to help
> the user, but that large a data list doesn't perform well enough to be
> helpful. I would either let the user type the claim number into a textbox,
> or use a combo box which only retrieves the row list after enough characters
> have been typed to limit it to a reasonable size list. Telerik components,
> for example, include a combobox which supports incremental data retrieval
> and I'm sure plenty of others can be found if you don't want to write all
> the code yourself.
>

Why "Access combo box"? It's about ASP.NET application with Access as
a back-end