ReportDocument.Load() Extremely slow and frustrating!

[Former Member]

Hi,

We have 3 workstations all with exactly the same hardware specs. The software specs are as follows:

Machine 1 - Win XP, VS 2008, CR 2008, SQL 2005

Machine 2 - Vista Business, VS 2008, CR 2008, SQL 2005

Machine 3 - Vista Business, VS 2008, CR 2008, SQL 2008

All the crystal assemblies are version 12.x

All of the machines are loading the exact same report files, and running the exact same code to do this, i.e the same project in VS.

Machine 1 takes about 5-7 seconds for the first load, then every other load after that, regardless of if it's the same report over and over, or different ones each time, take about 3-5 seconds.

Machine 2 takes about 5-7 seconds for the first load, then every other load after that, as above, regardless of if it's the same or a different report takes about 1 second to load.

Machine 3 takes anywhere from 1 minute up to two minutes, for the first and every other time a report is loaded.

We are stumped and have no idea what could be causing this.

Regards,

Paul M.

[Former Member · Accepted solution]

Hello Paul,

I would use a MS tool [Filemon|http://technet.microsoft.com/en-us/sysinternals/bb896642.aspx] to see what activities are actually going on all your 3 systems. Maybe that helps you to understand why machine 3 is so slow.

Falk

[Former Member]

Hi,

Just to make sure that your reports are referring to the final location for database rather than the database with which it is created, you can export the report in rpt format, open them in designer and check its connection properties by going to Field Explorer -> (Right Click) Set DataSource Location. Does they point to new or old location?

Regards,

AG.

[Former Member]

Strangely enough, it turned out to be the printer drivers for one of the printers on our local network. There must be something in that crystal method (.Load) which does something with the printers because as soon as we change the printer driver back to the old driver, the problem re-appears, we change it again and it disappears and the .Load is almost instant. We found this by chance as I noticed everything was working fine one day without the change of any code!

Hope this helps others who come across this issue.

[former_member208657]

In that case you might want to set the report to use "No Printer" in your Printer Setup options. This will remove your dependency on your default printer.

[former_member208657]

Make sure you are not using an SQL Expressions in your report. They can attempt to connect to the original database and cause load delays.

[ted_ueda]

> Machine 1 - Win XP, VS 2008, CR 2008, SQL 2005

> Machine 2 - Vista Business, VS 2008, CR 2008, SQL 2005

> Machine 3 - Vista Business, VS 2008, CR 2008, SQL 2008

So if you connect to SQL 2005 from Machine 3, do you get the same slow performance?

Sincerely,

Ted Ueda