Jim, when you include the ORDER clause in the SQL used to create the VIEW the subset will be ordered - no index will be created (just like regular cursors you know from the previous versions) and (again. like regular curors) you can create a temporary index on yjr subset you retrieved Arnon >Arnon, > >When one ORDERs a VIEW, does it create an actual index for it? > >regards, >Jim N > >>>It was I that asked about indexing a view the other day, and the >response >>>that I got was that no, you couldn't >> >>yes you can - see Tom's article in the VFUG march newsletter >> >>but you could base your grid on a >>>table that was written at runtime from the view and then index that. >This >>>is impractical for me, as the view I need indexed is about 100.000 >>records. >>>Is there another way? >>I wouldn't use views that retrieves that many records (or are you using >>fetch as needed) >>IAC , why not ORDER you view (when you create it) in the desired order >> >>Arnon > >