Hi Handy,

Sorry for the delay in testing this. I couldn't test the beta version on our production system and hoped that in the meantime a new stable version comes out. But as you moved to release 7, it looks like there are no more updates to version 6.

Yes, this hotfix seems to work for my sample. I just updated ISNet.WebUI.WebGrid.dll and ISNet.WebUI.WebGrid.Resources.dll from version 6.0.7200.218 to version 6.0.7200.220 and my sample doesn't crash anymore.

Let me know when the status of your control has made it from "nightly build hotfix" to a stable, tested version.

Thanks for your support.

Regards,

Eric

If found my problem. I have this code:

<RootTable DataKeyField="Block_Id">
	<Columns>
		<WebGridColumn Name="Description" DataMember="Detail_Name" />
		<WebGridColumn Name="BlockId" DataMember="Block_Id" />
		<WebGridColumn Name="ParentBlockId" DataMember="Parent_Block_Id" />
	</Columns>
	<SelfReferencingSettings ChildDataMember="Parent_Block_Id" Enabled="True" ParentDataMember="Block_Id" ExpandColumnMember="Description" LoadOnDemand="True" />
</RootTable>

The two attributes ChildDataMember and ParentDataMember both point to a DataMember value of WebGridColumns. But ExpandColumnMember ("Description" above) is not the DataMember of a WebGridColumn, but the Name of a WebGridColumn. So for the example above I have to use ExpandColumnMember="Description" instead of ExpandColumnMember="Detail_Name". The code above shows the corrected version.

Where I copied it from, both Name and DataMember were the same, so it worked there.

Unfortunately WebGrid doesn't give any error message if ExpandColumnMember is wrong or cannot be not found; it simply won't show the "plus" to expand the node.

One more info on this: The old application worked - at least regarding the unbound data handling. I think it's a bad design, but decide yourself. If I cannot find a better solution quickly, I'll will use this also. Here it is:

In Page_Load the data for the grid is loaded from the database. The full DataSet is stored in a Session variable. Then calls to grid.ClearCachedDataSource() grid.DataSource=(from session), then grid.DataBind(). The event grid_InitializeDataSource is not implemented.

When clicking the Add button, the modal popup, opened by JavaScript in the OnClientClick event selects the data and stores the ID in another session variable. In the button handler event (server side) the DataSet from the session is being read. A new DataRow is added and again grid.ClearCachedDataSource, grid.DataSource=, grid.DataBind is set.

I think it is bad to store the full dataset in the session (and also the ID of the selection dialog). If not other possible, at least ViewState for the DataSet should be used. But I think this data belongs to the WebGrid, and I should not cache this data in my code again.

Eric

Thanks for the update. I'll post feedback when I have tested it.

Hi Handy,

Thanks for the update. But before testing this, I need some more infos. We just bought the update to version 6 a few months ago. Will this version 7 component work with our license for version 6?

If your build has not been regression tested (whatever this means in detail), then I prefer not to use it on our production system yet. But of course I can test it to give you feedback if it works now.

Thanks,

Eric