No Printer tells the formatting engine to use some of the default printer properties and then it uses usp10.dll to format the report.
Not using No Printer is the best option.
No, unless you request the Job server to process the report in your app it will not use it. Only BOE viewing on demand or scheduled reports uses the Job Server and Cache servers.
Don
Rather than no printer select Dissociate, that removes the specific dependency on the printer the report was designed against.
Dissociate removes the specific printer from the report and will use the "Family" of printer properties.
For custom Paper sizes you do need to design the report with those printers.
Don
Also, if you move the reports to your web server instead of storing them in BO, you'll need to change the SDK that you're using to the Crystal for .NET SDK. This SDK has limitations on how many users can be viewing reports concurrently (5 sessions total) as well has how many "print jobs" can be open (100).
A print job is an instance of a main report or subreport. So, if your report has 1 main report and a subreport in the report header or footer, that counts as 2 print jobs. If the subreport is in a group or details section and there are 100 groups or detail records, then you have 101 print jobs and the report will fail.
You are probably better off keeping the reports in BO.
-Dell
Add comment