>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
>
Do you think this is a limitation on the use of views? For views with a great number of records, there may be no quick way to order them (e.g., for clicking on grid column headers for reordering), as with preset table
indexes?