READ FIRST
I re-wrote this to make it more readable. If you want to skip right to the chase, look at the ALL CAPS comments in the code blocks. All necessary code has been included for debugging.
I’ve searched multiple forums (including ASP.NET), and the MSDN library and cannot fix this >.<
GOAL: To dynamically generate a table/grid-like “status report” containing up to 20+ depending on user-specified columns (consideration: should be able to be stored in a cookie for user prefs). This grid will contain data provided from a View on the SQL Server, and row must be clickable. Pagination was super easy to implement, but the sorting has proven to be a nasty challenge.
ISSUE (Scope): I decided to re-post all the relevant code to make it easier to troubleshoot.
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
If Not IsPostBack Then
chooseColumns()
End If
End Sub
Protected Function queryToDataSet() As ArrayList
'Code removed: Function returns the Columns to select from
End Function
'Handles the button click to build the `GridView` from the selected columns
Protected Sub ShowGrid(ByVal sender As Object, ByVal e As EventArgs) Handles btnSub.Click
For Each item As ListItem In chkFields.Items
If item.Selected Then
Dim b As New BoundField()
b.DataField = item.Value
b.HeaderText = item.Value
b.SortExpression = item.Value
statusReportGrid.Columns.Add(b)
End If
Next
--> Me.GetData() 'HERE'S THE SCOPING ISSUE... UPON EXIT THE DATASOURCE IS LOST
End Sub
Private Sub GetData()
statusReportGrid.DataSource = StatusDS
statusReportGrid.DataBind()
End Sub
Protected Sub statusReportGrid_Sorting(ByVal sender As Object, ByVal e As GridViewSortEventArgs) Handles statusReportGrid.Sorting
'CODE BREAKS HERE because the DataSource is no longer in scope
Dim dataTable As DataTable = TryCast(statusReportGrid.DataSource, DataTable)
If dataTable IsNot Nothing Then
Dim dvSortedView As New DataView(dataTable)
'The following line (when working properly) should return a string
' something like "StatusColumn DESC" for example. This format
' doesn't make sense to me and doesn't seem correct.
dvSortedView.Sort = e.SortExpression + " " + getSortDirectionString(e.SortDirection)
statusReportGrid.DataSource = dvSortedView
statusReportGrid.DataBind()
End If
End Sub
Private Function getSortDirectionString(ByVal sortDirection As SortDirection) As String
Dim newSortDirection As String = String.Empty
Select Case sortDirection
Case sortDirection.Ascending
newSortDirection = "ASC"
Case sortDirection.Descending
newSortDirection = "DESC"
End Select
Return newSortDirection
End Function
ASP CONTROLS
GridView control (minus the styling stuff) – The tutorials I’ve read said to set the EnableViewState to false. When trying it with a setting of true I get repeated columns on refresh.
<asp:GridView ID="statusReportGrid" runat="server" AutoGenerateColumns="False"
AllowPaging="True" AllowSorting="True"
EnableViewState="False" ShowHeaderWhenEmpty="True"></asp:GridView>
Primary SqlDataSource control for the status report content.
<asp:SqlDataSource ID="StatusDS" runat="server"
ConnectionString="<%$ ConnectionStrings:StatusDBConnectionString %>"
SelectCommand="SELECT * FROM [StatusTable]">
</asp:SqlDataSource>
THE PROBLEM
I just discovered this to be an issue of scope as once my calling function that causes the DataSource to be bound to my GridView exits, the DataSource then becomes empty. I would certainly appreciate some help resolving my scoping issues so that my DataSource remains available and modifiable by all functions in the codebehind. It should be persistent as long as the page is being displayed more or less.
Here is an example of doing what you want without a DataSource Control, using a code behind DataTable & Cache along with a custom SortDirection function that manages the sort direction in the view state.
Here is my sample HTML control source that I used for the test….
Let me know if this makes sense, I don’t normally code in VB. The SortDirection is a known issue, because it always returns Ascending. As for the use of a DataTable vs SqlDataSource, both can be used but I find the DataTable approach easier.