Navigation Form with Large Number of Records - Help!

Navigation Form with Large Number of Records - Help!

Post by veeee » Fri, 24 Dec 2004 14:23:57


Hi

I have an application for my company's HR department where we store
resumes for candidates we receive. I have an application that uses
VB.Net and ADO.Net and data bindings (through code) to controls on a
Windows form. The question I have is that once the database grows and
contains a large number of records, I am worried the dataset is going
to create too much overhead when the user clicks "show all records"
(the full resume which contains a lot of text is retrieved for each
record so the dataset will contain lots of text for lots of records).
On the other hand, if I connect to the database everytime the user
clicks next / previous / first / or last, I am worried that the
application will run too slowly. Does anyone have any recomendations
as to which technique (or any others to use) will be better when the
database grows to a large (tens of thousands) number of records??
Sorry if this is a dumb question to anybody but I can't seem to find
any articles / books that address a topic like this. Thanks in advance
for your help!
 
 
 

Navigation Form with Large Number of Records - Help!

Post by Mike Willi » Fri, 24 Dec 2004 18:11:56


What's VB.Net?

 
 
 

Navigation Form with Large Number of Records - Help!

Post by veeee » Sat, 25 Dec 2004 01:23:36


bindings

Visual Basic.Net?
 
 
 

Navigation Form with Large Number of Records - Help!

Post by Mike Willi » Sat, 25 Dec 2004 01:49:10


Oh, I see. Is that really what it says on the box? Little *** s!
 
 
 

Navigation Form with Large Number of Records - Help!

Post by Randy Da » Sat, 25 Dec 2004 01:53:28


<echoing oracular voice>

Thy question is valid beyond the evil .net of
which you speak, and is thus deserving of an
answer. Speak not its name in this newsgroup
again, however! :)

</echoing oracular voice>


Do it like eBay or Google: compromise. What about
'next 20', 'first 50', or whatever number produces
a useful screenful of records to select from?

If all resumes are sequentially numbered, you
can modify your search to include "where resno>n
and resno<n+50", then substitute a new value for 'n'
in the search each time the user navigates.


HTH