Okkkk....

>>>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.
>>>
>>
>>But, Mike, why use Filter at all? Why not just a simple relation in the Data Environment or set up the relation using ChildOrder and other Grid properties?
>>
>>My rule of thumb is to avoid Filter like the plague...I only use it for ad-hoc browses. There is only so much optimization VFP can do to a Filter.
>>
>>There! I've given you an alternative to views. Although, IMHO, views are the way to go when you want a small subset of a heavily populated child table.
>
>
>I never said I was doing any parent-child stuff....

Ooops...I assumed. OK...in that case I don't see how you're getting around the View and filter issues without a SELECT - SQL statement or a conditional index.