crystal report slow performance at first time.

Question

0.00/5 (No votes)

See more:

Dear Expert,

My crystal report is working fine. But it very slow at the first time.
Is Backgroundworker the solution. Some body tells us to load a dummy report before its execution. But how to load a dummy report?

Regards,

Anil Kumar

Posted 25-Jan-15 4:23am

anil_kumar_bhakta

Add a Solution

Comments

DamithSL 25-Jan-15 10:26am

what you doing in first time and second time?
have you debug and check whether you are executing same activities in both times or not?

anil_kumar_bhakta 25-Jan-15 11:06am

yes. it is the same activity.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wendelius · Answer 1 · 2015-01-25T04:39:00

A very likely reason is that the time required to run the first report is high because all the necessary dll's etc need to be loaded. Basically you cannot remove this time but you can run some report in background when the program starts. This can be done in a background worker so that it doesn't affect the main program.

The report itself doesn't matter. Just create an empty report and run it in the background and close it as soon as the report is ready. The whole point is to get the dll's loaded so that when an actual report is run all the necessary assemblies are found in memory.