>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.

Walter,

You are making your own reality. Have you ever run a form with a filtered RecordSource for a grid that has a large number of records? If not then I can understand what you are saying. But if you have seen the abysmal preformance of a grid with a filtered RecordSource on it and still believe what you are saying is true, there is something very wrong with one of us.

Anyway, you and I will need to agree to disagree here because I absolutely sure convinced that the advice I give on this issue is the very best advice possible, and you are absolutely convinced that your point of view is better and never the twain shall meet.

I am convinced, beyond any reasonable doubt, that using SQL is generally the better way to limit the records in a set. I find it more scalable and flexible and I find that there is often no or little difference in performance (when both approaches are fully optimized). I may, someday, use a filter but right now I can't imagine when I would do it.