Hi sevans,
OK, the brief answer is that if you update say the opposition team in one control (say, the GridView) it won't be reflected in the other control (say, the DetailsView) because the values shown in that control are stored in ViewState and aren't refreshed until you either reopen the browser or force the page to update the viewstate for that control by making it change - the easiest way to do it is to try and edit the same match details in the control and when you click edit, the value you changed in the other control will appear in the other one.
So why does it work this way? Basically, it's to reduce the number of times data is retrieved from the database - if the two controls used the same datasource, they would both update, but they don't.
Is there a way to change this? Yes. You can disable ViewState for both GridView and DetailsView in two ways.
1. Select the GridView in design view on fixtures.aspx. In the properties window, set EnableViewState to false. Repeat for the DetailsView.
2. Switch to code view for fixtures.aspx. In the top line <% @Page ... /> add
EnableViewState="false" among the properties. VWD's autocomplete will help here.
Note that option 2 switches ViewState off for the entire page here, and not just the GridView and DetailsView. This doesn't matter too much for this page as it's just a demo for updating data to a database but I think it's worth noting that sometimes this isn't always the best thing.
Anyway, I hope that helps.
Dan
Dan Maharry
Read the feed at
http://feeds.feedburner.com/dansarchive