Moved to a brand new computer. Complete fresh install of TDA 3.4.
For some reason, all my reports that were set to print landscape are printing in portrait mode. Even if I open it in Design Report and go to Designer > Settings > Page Format > Landscape > True and save if off, I still find that the Landscape switch has been set back to Portrait. The preview looks fine.
I have even tried to create a fresh report, selecting Landscape and when I go into the Designer, it is set to Portrait.
These reports are run with a PDF export and then emailed to users as an attachment.
I have discovered the same problem after installing 3.4. Modifying ‘Landscape’ to True does not persist beyond the editing session. Also, all margin settings revert to ‘100 100 100 100’.
3.4 is unusable here without a workaround.
In addition, in 3.3 and 3.4, the rendering of the font I was using ‘Microsoft Sans Serif’ to PDF was virtually unreadable. See this excerpt:
You are correct the landscape attribute does not persist in the designer palette where it did in TDP 3.2. But neither TDP 3.2 or 3.4 used that attribute by default when pressing print. Don't you want to set up the report so that when ever you press print it will use landscape? It doesn't do this in TDP 3.2 either. I entered QAT-1373 for this isuse. Plesase clarify if I have some misunderstanding See image below.
We export reports to .pdf files via automation overnight, so users are not interactive with the report creation process. Any thoughts for that? Example:
What about the margin settings?
As for fonts, try exporting to PDF and see if you get the same results. I’m viewing results with Acrobat X btw.
As mentioned in the last post, that is exactly how we use the reports. They are output in a PDF and emailed to users.
I was using versions up to 3.3 and this worked. When originally building the report via the Designer wizard or changing the Landscape = True in the editor, it always persisted.
I regret that Toad for SQL Server currently does not have a patch available. The Toad for SQL Server Team has been advised of the issue and may implement the fix at a later time if enough resources are available to address this.
