I appear to have run into a performance problem when loading reports in an application when the printer used when designing the report is not available.

Below is the scenario as simply as i could explain it.

Report created on a machine and incorporated into an application. When app is built and run on a different machine on the network the report runs fine unless the Printer attached to the machine the report was originally created on is not available, it then seems to take between 20-30 seconds the access any of the reportDoc properties, (Eg, setting new database locations etc etc). If the printer is available (its a network printer) accessing the reportDoc properties is quick.

Have tried setting the report print options to "No Printer" but this didn't seem to have any effect, obviously this is goign to cause us a massive headache when our finished App is sent out to customers.

Any ideas ?