You can scroll in both directions, but scrolling to the 'last' record may cause memory problems. If it is just the last record(s) you are interested in, just sort the result set by using an appropriate order by clause.
If you need both the first and last records of a 200,000 record result set, then it may be a good idea to rethink this functionality. Why is the first and the last record of a 200,000 record result set important? Can they be queried in a more efficient way? How, for example, would you solve this in PL/SQL on the server?
------------------
Marco Kalter
Allround Automations