My application of a database requires developing super/subclass tables and relationships using SQL Server. For the superclass table, it is very easy to use RadGrid to develop both the structure and potential hierarchy relationships between each row in the table. However, I find it necessary to be able to display for each row in a superclass table unqiue data which belongs to the corresponding subclass. This requirement extends not only to the display of the data but also inserts and updates of the record. While RadGrid supports most of my requirements, how would one build such a RadGrid display using these requirements? I know I can use Templates to display data not shown in the RadGrid, such as from the CardView example, but what if there are 10 different subclass tables and each has unique structures and display?
2 Answers, 1 is accepted
0
Accepted
Hello Walter,
One possible option in this case would be to use a hierarchy. Or, you can use a nested view, as shown in this example. I hope this helps.
Best wishes,
Yavor
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
One possible option in this case would be to use a hierarchy. Or, you can use a nested view, as shown in this example. I hope this helps.
Best wishes,
Yavor
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Ceramist
Top achievements
Rank 1
Rank 1
answered on 12 Mar 2009, 11:39 PM
OK, the Grid/Hierarchy with Templates convinced me that this is the correct answer.
This structure permits associating all the possible subclass entities even to the point of specifying specific subclass entities can only belong to certain superclass entities. All I need to do is define a visual structure per subclass within the NestedViewTemplate along with an associated data provider.
The selling point for me was understanding that the NestedViewTemplate could handle multiple associated detailed tables.
What a wonderful product we have from Telerik!
This structure permits associating all the possible subclass entities even to the point of specifying specific subclass entities can only belong to certain superclass entities. All I need to do is define a visual structure per subclass within the NestedViewTemplate along with an associated data provider.
The selling point for me was understanding that the NestedViewTemplate could handle multiple associated detailed tables.
What a wonderful product we have from Telerik!