Mike.

I was already thinking about option 3, but wanted some validation for that option.  Options 1 & 2 look like they could turn out looking very confusing to a user that may just be getting started with our system.

Thanks,

Bob

Hi,

btesch said:

I know you are only the messenger, but I don't understand why the tool was build in such a way that this is not possible?  Why does it have to be limited to one main band and only childbands from there? 

I'm not sure why it was implemented this way. It's probably just because most applications do not display multiple tables in the same control.

btesch said:

What is your recommendation for dealing with this kind of data and have it appear as if there are multiple main bands that can be exported to Excel with the exporter?

As I see it, you have a few options.

1. You could create an artificial hierarchy. Basically, this means creating a root band with some rows in it and each row will show child data that comes from a different table. This is only possible if all of the child data is the same data structure (same columns). And it would require you to place your child tables into a single table so that you can access it using a relationship to the fake root table. This could get very confusing, and in fact, I'm having trouble outlining it because it's so complicated.
2. Another option would be to use UltraDataSource in virtual mode. This mode allows you to populate the data on-demand. What you do is set up the UltraDataSource with some row at the root level - one for each table you need. Then you handle the events of the UltraDataSource so that when it requests the data, you retrieve that data from whatever table or other data source you like. Once again, the child bands still have to have the same data structure because the grid cannot support non-homogeneous data.
3. Use multiple grids - one for each table you need to display. You can export multiple grids to the same Excel document.

By the way, in cases 1 and 2, I mentioned that the data structure of the child bands has to be the same. That's not entirely true. You could create a data structure where the root level has multiple child bands (as siblings to each other) with different data structures. Each parent row would only contain data for one child band and simply have no child rows for any other band. This would work, but it might be a bit confusing and inefficient, depending on the number of child bands you have.

Mike,

Mike Saltzman"]If you want to display hierarchical data in the grid, then you must have a single root band with child bands. You cannot display multiple root bands as siblings in the WinGrid.

I know you are only the messenger, but I don't understand why the tool was build in such a way that this is not possible?  Why does it have to be limited to one main band and only childbands from there? 

btesch said:

Not all data will be hierarchical.

What is your recommendation for dealing with this kind of data and have it appear as if there are multiple main bands that can be exported to Excel with the exporter?

Hi,

btesch said:

I need to be able to display multiple bands in a grid.  They may or may not be related to a "root band".  They may be segments of a report that are being displayed in a grid for the user to sort and mix.  Eventually, to send to an Excel spreadsheet.  Not all data will be hierarchical.  A lot will be.  How do you recommend to go knowing that the end result is proabably Excel.  Ideally, I would like to be able to add root bands, but the tool is too limited to accomplish that. 

I don't understand what you are asking. What do you mean that you may or may not have a root band?

If you want to display hierarchical data in the grid, then you must have a single root band with child bands. You cannot display multiple root bands as siblings in the WinGrid.

If your data is coming from multiple tables and you want to display it in a single list with no hierarchy, then you have to build a data structure with a single table. You could do this with UltraDataSource or by using a DataTable. But the data would have to be combined in the DataSource, it cannot be done in the grid.

btesch said:

<soapbox> BTW, your "email me replies" has not worked since I joined this list almost two years ago.  The problem I find out is that your email server sends url links that are not properly qualified and look like they have .com executables in them and they get rejected by our mail server.  </soapbox>

I will pass your comments along to the folks who maintain the forums. :)

I need to be able to display multiple bands in a grid.  They may or may not be related to a "root band".  They may be segments of a report that are being displayed in a grid for the user to sort and mix.  Eventually, to send to an Excel spreadsheet.  Not all data will be hierarchical.  A lot will be.  How do you recommend to go knowing that the end result is proabably Excel.  Ideally, I would like to be able to add root bands, but the tool is too limited to accomplish that. 

<soapbox> BTW, your "email me replies" has not worked since I joined this list almost two years ago.  The problem I find out is that your email server sends url links that are not properly qualified and look like they have .com executables in them and they get rejected by our mail server.  </soapbox>