I'm considering the upgrade again to address some missing features from version 10.5. Their documentation for fixed bugs do not mention this issue as having been fixed. Has anyone had any experience with the updated service packs (9 or 10)? I had to perform a difficult rollback to version 10.5 which I still use with visual studio 2013. The problem with this is that it added over a minute to the most basic print jobs. The only way to change the printer name at runtime was to create a new printer settings object and assign the required printer name. _report.PrintToPrinter(Settings, new PageSettings(), false) for version 13 you have to assign the printer settings This is the old and reliable way - didn't work for version 13
But I found that setting PrintOptions.PrinterName on the report document had no effect if the report already had a printer name. I upgraded to their latest developer version for Microsoft Visual Studio (13) a year or so ago, and installed the service pack 2. I've been using the Crystal report basic runtime 2008 (10.5) for over 3 years.
0 kommentar(er)
