Walter,

PMFJI - I've decided to be more active on the Thread in 2000 . Now all will know just how opinionated and annoying I can be since the last weeks of 1999 proved that these are OK charateristics to have on the thread :-) The good news is that I don't resort to name-calling or insults.

I agree with Jim - and most otheres that know what they are doing. Filters suck. There is almost ALWAYS a better way to handle a given situation. they should be removed from VFP with a bunch of other legacy code/functions. I have used them RARELY to filter SMALL data sets (such as related line items where I only want to see the line items of a certain type) but even that could be handled differently.

My .02,
Ken


>Jim,
>
>>>When all you want to do is poping up a maintainance form for unfiltered main tables (Articles, clients, employees) where the default is non-filtered you don't want a delay of a few seconds. The form should pop-up inmediately.
>>
>>I design for scalability and Client/Server access. I never pop up a maintenance form with a full recordset loaded. In my forms, the user specifies what they want and then I get that for them.
>
>That's the difference, I don't design for scalability for C/S system if I suspect that the system will never be upsized to a C/S environment, giving me more flexibility at the UI side.
>
>My users can freely browse through the tabel and I provide some powerfull search mechanisms to find the data the user needs. Filtering tables is one of them.
>
>Walter,