Re: Fetching more records for a grid

Jeff Grippe wrote:
Here's the big BUT

BUT I need to maintain some type of similar UI from the old form
(which used the giant table as the recordsource for the grid) to the
new one which only loads 100 records at a time.

So you want a paradigm change without any actual change? <g>


Here are the problems:

1. The application has always opened to the first screen full of data
in the table. It does not begin with a search. It is after the form
is displayed that the search can be performed. This is not a problem.
The only real problem is...

2. Sometimes they actually do want to browse through several hundred
or even a few thousand records. They might search for the first one
but then browse through an entire account.

As I said, parameterized views are great for this. Construct the query so
the where clause is "Like ?lcParameter", where you've tacked the wildcard
character (%) onto the user-entered parameter and requery() the view. You'll
get back whatever matches and the user can browse the result set.

You need to get away from thinking "next n" because the ONLY database where
that has any meaning is Foxpro. The concept simply doesn't exist in
databases where data is defined logically rather than physically (which is
all of them except VFP).

Dan


.

Loading