I was working on a book yesterday, all was fine when I closed down. Today when I viewed the book again the pages had become a distorted landscape (the text is small as is spacing) rather than the usual A4 portrait. I have the same problem with any new reports I generate. The problem also occurs if I generate a new report in other projects including the sample project. However some 'old' books in other projects including the sample project do display correctly. When I output the distorted report as rtf then the page size is reported as 'user defined' not A4 landscape. If I try to output as pdf I get an error message. I have tried to alter the orientation in report options but nothing happens when switching from portrait to landscape and back, it just stays the same. Otherwise things appear to be working normally. I am using v6 and running Windows 10. Any suggestions would be very welcome.
Colin
* Report page orientation problems
-
chstevenson
- Silver
- Posts: 5
- Joined: 20 Sep 2014 13:54
- Family Historian: V6.2
- Location: Shropshire, England
- tatewise
- Megastar
- Posts: 27088
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Report page orientation problems
Hi Colin.
Check the File > Print Setup settings.
What Paper Size, etc, is selected?
Make sure it is set to A4 210x297mm Portrait.
Also it is best if Printer Name is Family Historian PDF.
Check the File > Print Setup settings.
What Paper Size, etc, is selected?
Make sure it is set to A4 210x297mm Portrait.
Also it is best if Printer Name is Family Historian PDF.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
-
chstevenson
- Silver
- Posts: 5
- Joined: 20 Sep 2014 13:54
- Family Historian: V6.2
- Location: Shropshire, England
Re: Report page orientation problems
Thanks Mike. However, problem now solved. I restarted my PC this evening and on opening FH found things were back to normal. I had tried closing and opening FH a couple of times but it made no difference. I forgot the basic rule, if something is not working switch it off and switch it on again. The problem seemed so localised that I thought it must have been within FH. Sorry to bother you.
Thanks again.
Colin
Thanks again.
Colin