Hi guys, I am wondering if it would be possible to create a single DataTable and then use some sort of "grouping" functionality to create a hierarchy suitable for the grid. Basically right now I create multiple stored procedures that populate data tables, and then I create a relationship between the tables and bind them to the grid. I am wondering if I could just write one stored procedure with a larger join based select statement that will give me a flat representation of the hierarchy, then somehow define the grouping and bind it to the gird. I believe this is how MS Reporting Services works, where I can define the "grouping" columns from within a single source, in essence producing a hierarchy. I'm using 7.2 controls if that matters. What I am trying to accomplish is having less stored procedures, especially specialized procedures that will likely never be used outside of my screen. If all fails I think I can just go the multiple select statements in one procedure route as well. All and any ideas are welcome!
Thanks,
Not really what you're asking for, but... You could pull back a big, honkin' datareader from a single proc, then loop through and build datatables from it, then add them to a dataset and slap in a relation and bind it.
I'm not sure it's worth the effort to do this though.
gernblandston said:Not really what you're asking for, but... You could pull back a big, honkin' datareader from a single proc, then loop through and build datatables from it, then add them to a dataset and slap in a relation and bind it. I'm not sure it's worth the effort to do this though.
Yes that's the way I would do it right now, I would have one stored procedure with multiple select statements for example. I just thought perhaps there is a feature such as what I described in my original post. As far as I know reporting services does it, as well as crystal reports.
No, I was thinking more along the lines of:
>>I could just write one stored procedure with a larger join based select statement that will give me a flat representation of the hierarchy <<
Which would return a single datareader/datatable, then you would loop through it and build the multiple tables from that manually.
This would accomplish your goal of generalizing your proc and still allow you to present hierarchically.
From a maintenance perspective, I'd opt for multiple, simpler procs than trying to put everything in one basket.
gernblandston said: From a maintenance perspective, I'd opt for multiple, simpler procs than trying to put everything in one basket.
The way you're doing it now is the way the grid is designed to work. It would take a really compelling reason to get me to try and buck that system.