Sorry 
What we have done is use the display objects to do this type of searching 
(Query by form). I.e. the paramaters which are searched by (queried by) 
are passed to the load of the display class. It then dynamically builds 
the SQL and loads from the database. This does mean that if the user then 
changes or modifies his/her query the data will be reloaded (some 
performance issues). 

Using an ADO recordset to achieve this also has impacts - If you are doing 
the n-tier version or wish you solution to be scaleable then you would 
have to marshal the recordset from the server. This is not as efficient as 
the other object streaming methods used in CSLA. You could then do this 
type of filtering etc on it. The display object would then have to hold 
the recordset or something like that. 
I would go for the first solution and if performance becomes an issue then 
look for alternates.

Another option which we are just starting to investigate is to have the 
display object return an XML and then to use XSL or XQL to carry out the 
query.

Regarding databinding the professional vb6 distributed bus obj book covers 
the ODSOLEDB dll this can be used to databind bus objects or collections 
(display collections or parent child collections) to datagrids, textboxes, 
combo boxes etc.

Regarding books : Both the Lhotka books and then some windows DNA, Com 
books.

Brett