>>Hi All.
>>
>>I just want to gripe about the fact that filters and grids are still apparently a problem in VFP 6. I think it really stupid that I can open a large table and set a filter and browse brings up the data in seconds while a form with the same table in its data environment with the same filter and a grid connected to the same table takes minutes.
>>
>>And don't anyone tell me to use a view. I already know that and that is not the only answer to application development. If it was, the BROWSE command would never have been Rushmore aware and Rushmore optimization would never have been invented and LAN based applications would never have been made without a database server backend.
>>
>>Thanks
>>
>>Mike Yearwood, GE Capital Consulting
>Mike,
>
>Gee, you seem ticked. Perhaps a SELECT command would be faster than the filter?

Hi Jim,

You know we've had this discussion before <g>. I'm not ticked, just frustrated. A SELECT is no better than a view (actually its worse since it doesn't provide all the cool stuff views do). It used to be really cool to open up a large table, and browse it (and reorder on the fly and filter on the fly). What's wrong with that? I really liked being able to do that without really having to specify what I wanted.

Further what about this... If I set fetch as needed from a SQL server back end and tell it to send one record at a time, and USE a view that has no order, I get records very quickly. If I add an order by clause, the back end appears to produce a new output set ordered as specified and then starts sending the records.

What a frustration it would be if your car required explicit destination and speed information before you could drive it around. How about if you went into a store and the sales people wouldn't let you just look around?

I know I'm not the only one who would like this behavior.

Mike