I have a very complex report which lots of fields and 3 subReport elements. The report size is set to fit on A5 paper and when printing correctly prints the main part of the report on the front of the paper and if data is present prints the subReports on the back - i.e. double-sided printing. It has worked successfully for many years, but has recently started to misbehave on one user's system.
The setup is quite simple. I have a development system where I produce updates to the main .accdb file. The latest .accdb file is uploaded to a file server and 2 pc's download a copy of the .accdb file and begin operation.
There have been no changes to the code in the area of the report in question.
The development machine has a small Epson printer and the 2 production pc's have large HP LaserJet printers (LAN connected)
Viewing the page set up of the report on the development machine shows this:
When the app is loaded on the first production pc the same page set up shows
And this pc produces the report correctly
But the 2nd production pc shows this:-
And thus prints to A4 (and single sided!) If I change the settings on this second pc to A5 then it does indeed print to A5 but still single sided - the report on one piece of paper and either a blank page or the expected second side (depending on the contents of the subreports.
Exactly the same thing happens if I swop the printers by changing the default printers - so the 2 pc's use the other's printers.
So my question is - where are the page set up details stored or acquired from as it appears that they are not properly burned into the accdb file??