well kind of my point... you are going to have a harder time converting whatever it is that the user selects to translate it to some xml search... think of the alternative... let's say your buttonclick does something like...
Code:
button_click_handler(){
int i = (int)dropdownlist.selectedindex;
string cmd = "select * from tbl_recipe where tbl_recipe_PKID = " + i;
// from there- go on to query the database and return that record
a heck of a lot less code and effort than parsing through some XML file. XML files are a way to get unrelated languages to talk to each other- they shouldn't be used as datatable structures... it becomes a nightmare real quick when you do that
... let's say you get your XML 'template' set up... and let's say you have 3 records
Code:
<tbl>
<IDCol>1</IDCol>
<txt>Demo</txt>
</tbl>
<tbl>
<IDCol>2</IDCol>
<txt>Demo2</txt>
</tbl>
<tbl>
<IDCol>3</IDCol>
<txt>Demo3</txt>
</tbl>
now let's say there is an oops...
Code:
<tbl>
<IDCol>1</IDCol>
<txt>Demo</txt>
</tbl>
<tbl>
<IDCol>2</IDCol>
<txt>Demo2</txt>
</tbl>
<tbl>
<IDCol>3</IDCol>
<txt>Demo3</txt>
</tbl>
<tbl>
<IDCol>4<IDCol> <!-- note missing '/' -->
<txt>oops</txt>
</tbl>
your now 'expected' 4 record return with one table, will return an entire set with the data strewn about randomly. it sux