To filter data in a query, open it in Datasheet View, click the down-arrow at the top of a column, and select a filter option. You can select multiple values from the list, but in an app, the filter list closes each time you select an option.
I assume that you mean ‘pick up rows from a table’. I also assume that you have a particular constraint in mind (‘price has to be higher than $50’ or some such) or so what attribute you have to use is fixed (in the example, ‘price’). If this is the case, the only thing you can do in SQL is to have the proper condition on the WHERE clause of your SELECT statement. With the condition fixed, making the retrieval faster can only be helped by physical optimization. You can create an index on the attribute of interest (‘price’), but that index may or may not be used depending on several factors, mainly the selectivity of the condition (how many tuples the system expects to retrieve). You can try to pre-fetch the data and have it in memory (in some systems, it is simply a matter of giving the database as much RAM as possible and then doing a SELECT * from the table; in others, it’s more complicated). However, there is not a unique way that will work under all circumstances; much depends on system characteristics (database size, etc.). The time can even vary depending on other, unrelated SQL statements (i.e. if the database is handling updates at the same time, that may create a slowdown), so I’m not sure there is a single good answer for your question -at least without much more information.