Hi David,
Ah, yes of course.... SavedPrinterName is read only and that is by design because you are getting the info from the RPT file itself.
I had to change my code because of the way I was using the PrinterName, so it's all in the way you were using the Property... Sorry I didn't think of other scenarios that developers would be using that property. so for you all you need to do is leave your code as is and just recompile.
The reason it crashed the app is because likely the pointer for the API's changed, so simply recompiling should resolve that error.
With the new property now you can get the printer the report was designed with. So if the Design printer is not found you now have the ability to know what it was and can handle the messaging.
Those WIKI's are the beginning of how this will all work:
http://scn.sap.com/docs/DOC-58131
http://scn.sap.com/docs/DOC-57979
http://scn.sap.com/docs/DOC-58131
This will now allow you to handle the printer the same as we do in CR Designer, if you get a report that you don't have the printer installed you get the message:
Image may be NSFW.
Clik here to view.
Now you can manage that part also if you have reports that are designed specifically for a specific printers. This is the goal for these new properties and work flows.
When CR and BI 4.x are updated and released, now when printing a report with a custom paper size from a work station using the ActiveX Viewer it will look for the Printer, then the ENUM the custom paper size has assigned to it and the if that enum is not found or different than what the Custom Paper size Name when the report was designed the PrintControl dll will find the paper by name and not by ENUM. The same printer driver must be installed on each work station and the custom paper size must be exactly the same on the Server and Work station. Then the user should simply be able to hit the Print button, the PrintControl dll should find and set the correct printer and paper and the user does not have to go browsing for it each time they print.
I'll set a time next week to properly kbase this and update this thread also. I'll also update the Warning on the download page...
Don
