>>Do you mean SELECT one record (row) cursors, rather than pointing to a >>specific row (in a multi-row cursor) based on its logical position relative >>to another row?

As a rule, SQL Server can work with data as a set faster than it can respond to an iterative series of commands. However, if you feel you need to work one row at a time, then a cursor's result set can be navigated with the NEXT, PRIOR, FIRST and LAST arguments of the FETCH command. Check it out in SQL Server Books on Line.

Charlie