Pagination of data in listbox

[Guest]

I need some resources to understand best practices when filling a listbox
with a large datatable. I've got the basics down of making calls to the
database returning a couple hundred rows at a time on a separate thread, but
I still get a flickery listbox as each new page is added to the underlying
datasource.

Surely, I'm not the first to do this, so where can I read more about it?

Thanks in advance...

 

[Cor Ligthert]

Zorpiedman,

How do you fill it now because there are so many options in that?

Best practise does not exist in dotNet, it is not Ms-Access, when there was
a best practise there was only one method.

Cor

 

[Cor Ligthert]

I forgot, what is your database because that is as well important, Access by
instance is very slow when you compare it with SQL(MSDE) when you use huge
amounts of data.

And why the multithreading, seems to me crazy. I nowhere saw that that is
adviced to get data into an application from a database. That is in my
opinion sure no best practise.

Don't forget that when there is not a multiprocessing environment (more
processors or hyperthreading) there is never more than one thread working at
the same time. That has to be processed than extra to give every thread
entrance too the processor.

Cor

 

[Guest]

Cor -

It must be a language translation thing, but your responses always seem so
rude! We are not all idiots, you know!

Anyway, I have a MSSQL back end, and the list box is filled with the
datasource property.

I'm sorry you think this is so _crazy_, but it is the precise method I was
shown at a trainins session I took at the Microsoft campus in Redmond,
Washington. Yes, we all know it still takes as long (in fact a little
longer) since I don't have any extra processors, but the PRECEIVED speed is
what we are after. Get the data on the screen foer the user, than continue
filling it while they are deciding what to do.

 

[Cor Ligthert]

Zorpiedoman,

I did not see before I wrote this message that this was a message repeating
another message before this one from you where it seems you did not even
look or paid attention to the answer.

http://groups-beta.google.com/group/microsoft.public.dotnet.languages.vb/msg/4f2aa9685ef99f69

This is in my opinion in contradiction with this reply from you.

A lot of success with your (standard) solution of the problem.

Cor

 

[Guest]

Cor -

Please do not respond to any more of my posts. I find your
condensending remarks unproductive, and not appropriate for this forum. If
you have useful information to share with people, than share it, otherwise
keep your snide remarks to yourself. Many times people have to ask questions
more than once in different ways to try and get an answer. Becides, if YOU
really were paying attention, you would have seen that it was ME that
responded to my own question on the other thread once I found an answer to
that question. The problem has not gone away, and this new question is
trying to get more info.

If you don't have an solution, then just don't respond. I don't have
time to argue with someong over the quality or quantity of my questions.

Thank you.

-Zorpy