Thank you, I will try the UltraWinTree for cases where I don't need those few features and in the case where those are needed I will put a simpler datasource to only expose wanted data to the UltraGrid.

The issue is that I have a complicated data structure built on Entity Framework with relationships throughout the object structure.

I am using lazy loading as well so as soon as a navigation property is referenced then the data is loaded. In this case unnecessarily so. (or so it seems looking at the way the UltraGrid currently handles these properties).

When I load the data into the form I do not want 7 extra bands of data added due to this. I could modify my object structure or create derived classes specifically for the interface sothe grid shows/loads only what I want. It sort of defeats the purpose of the architecture of my project as it sits as usually I only one 1 or 2 of the bands on the grid. My opinion is the same of the extra columns which do not need to be there, I know they can be hidden but sometimes that data does not need to be bound at all and would be handled lower in the data structure but public for other reasons, not bound (hidden or not) on the interface where it could potentially cause other issues that need workarounds.

Hopefully that makes sense.

Looking for recommendations here at this point.