Hi there,
I noticed a very strage behavior while creating a PDF-report:
it's a quite simple report with a table with data from an objectDataSource.datamenber (a method that collects the needed data elsewhere)
If I just show the output on screen with the reportviewer everything works as expected.
But if I switch to only PDF-output, I got a second thread "rendering" and BOTH threads do use the datamember so it runs twice delivering exactley the same data. So my output tooks twice as long.
So why do both threads (rendering and "main") are using the objectDataSource? Can I somehow deny spawning a second thread?
Thanks in advance!
I noticed a very strage behavior while creating a PDF-report:
it's a quite simple report with a table with data from an objectDataSource.datamenber (a method that collects the needed data elsewhere)
If I just show the output on screen with the reportviewer everything works as expected.
But if I switch to only PDF-output, I got a second thread "rendering" and BOTH threads do use the datamember so it runs twice delivering exactley the same data. So my output tooks twice as long.
So why do both threads (rendering and "main") are using the objectDataSource? Can I somehow deny spawning a second thread?
Thanks in advance!