L
lilfos
I'm surprised that I haven't found more posts about the issues I'm
having. I did spend a long time looking before I decided to post.
We are using VS.NET 2005 with SP1 to design reports and embed them in
an aspnet web app. Some of them take a while to run, even in the
designer. In the designer, however, next page and print operations
are speedy.
In the web viewer, next page and print operations are agonizingly
slow. At first, I thought the buttons weren't responding.
Eventually, I realized that they were just taking their time.
Viewing page 2 of a report seems to take about as long as viewing page
1. It would appear that the entire report is being re-run and just
page 2 is being sent to the browser. Is this right? Shouldn't the
report document be stored on the server or event the client so that
the desired page can be loaded without having to hit the database
again??
Thanks!
having. I did spend a long time looking before I decided to post.
We are using VS.NET 2005 with SP1 to design reports and embed them in
an aspnet web app. Some of them take a while to run, even in the
designer. In the designer, however, next page and print operations
are speedy.
In the web viewer, next page and print operations are agonizingly
slow. At first, I thought the buttons weren't responding.
Eventually, I realized that they were just taking their time.
Viewing page 2 of a report seems to take about as long as viewing page
1. It would appear that the entire report is being re-run and just
page 2 is being sent to the browser. Is this right? Shouldn't the
report document be stored on the server or event the client so that
the desired page can be loaded without having to hit the database
again??
Thanks!