| 
					
						 Hi all.
 
 I'm facing the issue of providing the user of my applications with easy-to-use search forms. In my mind, a search form is structured as a grid whose columns are the "most important properties" of an entity, those to be searched in.
 
 Before NHibernate I was used to ask for the "Search Service" in this way:
 
 int ok = Search(Connection, TableName, VisibleFieldsList, IndexFieldName, SortedFieldName, WinCaption, ref IndexValue);
 
 The function shows a grid directly bound to a DBSource and populated with data retrieved by a dynamically created sql statement. The user, while searching for a row can re-sort records, filter by any column, etc...
 
 Though strongly bound to all-the-DB-stuff, this approach has the great advantage of allowing an easy search on virtually any table in my DB.
 
 What is the NHibernate couterpart for this approach, if any?
 
 Thanx,
 Marcello. 
					
  
						
					 |