>>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?
>>
>
>
>Bruce,
> the idea behind views is to save network traffic- by retrieving only the
>subset needed from the server
>big views kind of goes against that concept in the first place
>
That's pretty much what I was thinking...I've been in the habit of categorically using/recommending views for many situations without really considering size they may reach...but I'm going to give it more attention in the future...