# GrapeCity.ActiveReports.Export.Excel.Section.XlsExport.MultiSheet

## Content

<div class="doc-site-dotnet-api-container">



<h1 id="GrapeCity_ActiveReports_Export_Excel_Section_XlsExport_MultiSheet_" data-uid="GrapeCity.ActiveReports.Export.Excel.Section.XlsExport.MultiSheet*">MultiSheet Property
</h1>
<div class="markdown level0 summary"></div>
<div class="markdown level0 conceptual"></div>



<a id="GrapeCity_ActiveReports_Export_Excel_Section_XlsExport_MultiSheet_" data-uid="GrapeCity.ActiveReports.Export.Excel.Section.XlsExport.MultiSheet*"></a>
<h4 id="GrapeCity_ActiveReports_Export_Excel_Section_XlsExport_MultiSheet" data-uid="GrapeCity.ActiveReports.Export.Excel.Section.XlsExport.MultiSheet">MultiSheet</h4>
<div class="markdown level1 summary"><p>Sets or returns whether each page is to be exported to it's own sheet or not.  True indicates that each page in the ActiveReport Document will be exported to a separate sheet.</p>
</div>
<div class="markdown level1 conceptual"></div>
<h5 class="declaration">Declaration</h5>
<div class="codewrapper">
  <pre><code class="lang-csharp hljs">public bool MultiSheet { get; set; }</code></pre>
</div>
<h5 id="GrapeCity_ActiveReports_Export_Excel_Section_XlsExport_MultiSheet_remarks">Remarks</h5>
<div class="markdown level1 remarks"><p>Setting this value to true can often increase performance and output quality at the cost of memory consumption up to a certain number of pages.  The more complex the pages, and the more deviation between the page's layouts in a single document will lower the number of pages that should be exported to a single sheet. As mentioned, the complicity and deviation of layout between the pages drastically effects this number, but a guess would be greater than 30 pages would be suitable for MultiSheet=false.</p>
</div>
</div>