PaperSize hell

[patrick_simons2]

First if I try to save a Page Setup (using CR 2016 SP5) for a Dymo label printer, CR doesn't keep the papersize. After changing to the correct values I save the report:

then I close the report and I reopen it:

and the 11354 has gone away. Any ideas?

Also when using Don's test program, the correct papersize is also missing:

As you see the PaperSize is already wrong after opening the report:

PS. I'm testing RAS using CR VS.Net SP22.

Another question: would it be possible to save the 11354-papersize back to the original reportfile using RAS (SaveAs-method)?

Regards,

Patrick

[former_member11696]

Hi Patrick,

Ah, thanks for adding the platform info.

Redirect has always been a problem for the Framework and CRD. It's the nature of Easy Print ( what MS calls it ). It sends a virtual printer driver to the work stations, but the problem is CR Designer has no access to it, other than from the registry. There is no physical printer driver to get the info from. DEVMODE(W) is what CRD uses, since it doesn't exist only option is to use the properties of the users Default printer on the local PC which if no printer found we then can only use USP10 to format the report and it is not capable of creating a custom paper size.

So when you design the report with the Dymo Printer CR copies those settings into the report, now when No Printer is used it will use what is saved in the RPT file and not try to find "the best" fit when printing is done.

So it all makes sense now that the driver is installed locally, CR Designer has ALWAYS required the printer to be installed locally, it access DEVMODE - DM mode to get the customer properties. CR for VS uses the Framework to get the printer properties and uses it to do the printing, if the framework has issues with Easy Print again it's not something we can ask them to change.

As for asking MS to fix their Easy Print driver it's not something we can do. It's their product and the Users use it as is, We have no power to suggest they change it , it has to come from the end users.

Thanks again

Don