>Hi, Einar,
>
>I can't say that I've tried to move the lag to start-up, only because I have some users who seldom run reports.
>
>My personal advice is to just keep it the way it is - but if you need to do something, you may want to consider constructing a blank "stub" report that you instantiate at start-up. Create an instance, but then release it or something (as opposed to generating it). Just a thought.
>
>I'm not aware of any way to load the Crystal runtime without actually instantiating a report - maybe someone else here has an idea.
>
>Kevin

Thanks for replying Kevin. I understand your reasoning for never investigating this before, because I thought like this up until the day I posted this :)

Here are the reasons I want to research this:

1. The lag is not very long, but it is anoyingly long when trying to print a report.
2. The lag is not very long, and it would be almost undetectable during app start (especially if you have a pretty splash screen that keeps the users entertained<s>)


Well maybe I am just being very picky about that fraction of a second extra that the 1st report takes.

Thanks for the pointers. I will post back to the thread if I find something else when I acctually start coding this.

Einar