I think I have a complicated one here.
Synopsis: I have a AJAX enabled ASP.Net application, the purpose of which is to allow users to ad hoc drill an engineering database. The application UI is divided into three sections, Filtering, Column Selection, and Results. The filtering section (implemented as a user web control) uses a PlaceHolder control, to which I allow addition and removal of individual Filter user controls.
All of that works well. The Filter user control essentially consists of three ComboBox controls with SqlDataSources bound to each of those ComboBoxes, and a TextBox to enter in a value. The first ComboBox, once a value is selected in its list, passes the SelectedValue to the SqlDataSource of the next ComboBox, which uses that value as a Select Parameter so the DataSource can fill out the ListItems of the next ComboBox. So simply, the results of the previous one cascade to the next.
Again, all this worked well. But one of the requirements was to allow storage of these queries the customer comes up with, allowing them to reload the query at a later time to run again.
I implemented that by writing a simple set of container classes, Filter, Column, and Query, where Query has public arrays of Filters and Columns. I serialize that simple Query object, then store it as XML in my database. To reload i
View Complete Post