There are several ways to handle this. It depends on the number of
accesses, required response, DB server load.....
1. Have each user session allocated a unique session ID and record the range
they have last accessed in a SID table. Note that anything like this
precludes the use of straight HTML as the SID value needs to be included in
every form and URL.
2. Include the next and previous row IDs of the dataset in the Next and
Prior button URLs.
3. Load the dataset into a textfile and use an index into this as the
navigating pointer - not live, but doesn't load the DB and is very fast.
Only useful if the underliying data is not changing much. I've used this
with search results so that a complex query is run only once and the
resulting data is available for browsing or subselects.
4. Use a TCP/IP socket or COM application to cache the dataset or keep the
query alive for navigation.
I must admit that I have never figured how to identify a user session from
the server parameters available to a CGI/ISAPI. If the app could see the
session id from the server life would be a lot simpler.
HTH
Stephen Bertram
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
