[DevExpress Support Team: CLONED FROM T853147: Master-Detail - Large memory consumption when exporting expanded master rows]
I see… that's a pity. With the data volume of our customers the export function will not be usable with a master-detail-grid.
One suggestion: if i call "cxGrid1DBTableView1.ViewData.Expand(False)" the full expansion is very fast. We almost only have one Detail-View.
If i understand correctly the "ARecurse" parameter is responible for expanding the detail views. But since there are no detail views to expand, shouldn't it be possible to only create the Datacontrollers when you need to?
Meaning in our case the expansion before the export should work as fast as the expanion with "ARecurse" = false.
Thank you for creating a new Ticket. It is marked as fixed but of course it is not. Probably because the original Ticket is solved. Just saying … :)
You are absolutely right. Thanks.
We have found some ways to improve the performance in this scenario and we are going to use them in future builds.
However, this cannot help with exporting 5000 detail views in any case. Even if we reduce the export time by 50%, it will still be too long.
When using ViewData.Expand(False), our grid control creates only visible detail views. And other views are create on demand when scrolling. So, this option did not help as make export faster.