Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
147
Picking which DataTables to Show in the UltraWebGrid
posted

I've been combing documentation, the API's and this forum, but I am coming up a little short for my situation.

I have a DataSet with 3 DataTables.

ParentDataTable

ChildOneDataTable

ChildTwoDataTable

Each ChildDataTable is tied back to the ParentDataTable with a relation.

I would like to specify to show the the data in a heirarchical view between the ParentDataTable and ChildTwoDataTable.

I am setting the WebGrid.DataSource property in the code behind and then calling the DataBind Method.

How do I specify to show two bands and bind to the appropriate datatables in the dataset? 

The version I'm using is NetAdvantage 3.5.

Parents
No Data
Reply
  • 1414
    Verified Answer
    posted

    elamberton,

    Along the lines of WombatEd, here is a concept to try...Since you can pre-fill a WebCombo with the names of the two/three/four/... potential child tables you should be able to drive your active relationship off that selection.It is obvious you can do so using a WebCombo not attached to the grid.  Just change your relationship in code when the customer changes the option in the WebCombo.  When you perform a DataBind the grid should reload based on your 'new' dataset (ie. your master datatable and the selected child).  Should get pretty plusses and everything.An intriguing solution would be to attach the WebCombo to a cell in the grid.  You should be able to do so because the contents of the WebCombo can be pre-filled (the contents are known) and thus not 'filtered out' when the customer selects one child table over the other.  That probably could be made to look like the Microsoft Access process of choosing a child table to view when the parent has multiple sibling tables.Sorry about not being able to post code.  I am at home drinking some very good coffee - and thus away from my programming system.  The concepts intrigue me though - and I may attempt them at some point in the near future.

    By the way, me thinks you should consider upgrading.  None of these ideas may work on a tool that is five years old.  Back in 2003 (My guess based on the version being NetAdvantage 3.5) the Infragistics libraries were good for their day - but, not so good based on 2008.  I am not and Infragistics employee.  And, I don't sell any products.

Children