Vince,

I enjoyed your book. The framework and implemenation pattern provide a clean, simple and concise approach. I followed most of the code; although, the Workflow coding will require more study. I'm now more informed on how certain functionality can be implemented. A future implementation project will definitely include some of what I've learned from this book, perhaps, even retrofitted into a current project.

Can the pattern be easily adapted to provide selection fields, such as date range or status, before returning the result set and finally going to the single record for updating? Would you put the query fields and the resultset on the same page? There is placement of the Add button and the requery to consider, as well. This seems like a natural extension to the pattern.

Thanks for any thoughts you may have.
Tom

Hi Tom,
Yes, the query builder can easily be placed on a page with the grid view to display the results of the query. That was one reason why it was implemented as a control so that it can return a resultset and you can display it on a report, html table, or even export it to a text file. Another nice enhancement is the ability to save the query. You can easily persist the filters in the query builder to some tables in the database and then simply run the queries either on demand or on a schedule.
Another enhancement if you schedule the queries would be to add the ability to use date variables instead of hard coded dates. For example, you could say "Inserted Date > Now - 7" to get all records inserted in the last week.
Hope this helps,
Vince