How about a *bad* idea? < s > Would it help to break it out into a backend request for data and a front end limiting what's viewed? It's too fuzzy, to my mind, to do it all in one grab. Just a thought...

>>I list this in Client/Server because the solution needs to deal with either a VFP database or some other backend (Oracle, SQL-Server). I need to be able to draw, let's say 200 records, 100 before and 100 after some specific record. How the user gets to the specific record will be handled typically by incremental searching. The desire is to only bring a limited number of records across the network and to display that limited record set. Of course this must be highly dynamic as the user changes positions in the entire table/view.
...snip