Canon GP35 Landscape.

Posted by: ingare on 4 August 2017, 2:50 pm EST

  • Posted 4 August 2017, 2:50 pm EST

    We have a customer with a Canon GP35 printer that has trouble with printing in Landscape.



    We are using arpro2.dll ver=2.4.0.1279. 



    The printer is set to Portrait as default. When the customer try to
    print a Landscape report, it prints in Portrait. (The reports set the
    orientation like this:  rpt.PageSettings.Orientation=ddOLandscape)

    This works fine with arpro2.dll ver = 2.0.0.1195.  It also works fine with other printers



    What has happened in the new version and how can we solve this?








  • Replied 4 August 2017, 2:50 pm EST

    You will want to make sure the printer driver supports the size of margins as well as landscape printing.  If the margin/paper size selected is not supported by the driver, ActiveReports will render/print the report with the printer's default settings, changing from landscape to portrait.  To test if your margins/paper size are supported you can try to print a word document with the same settings as the report.  If there is an error from wordpad and it changes your margin settings, you will know the driver does not support the settings.
  • Replied 4 August 2017, 2:50 pm EST

    First of all:  The printer is a Canon GP335 and not GP35 as I wrote and it support landscape printing. (Sorry).


    The landscape-printing works fine with arpro2.dll v2.0.0.1195 but not with arpro2.dll v2.4.0.1279.   You write that the customer need to check the margins.


    Why does this not work with the new version, are there any new restrictions with the new version?


    Ingar.

  • Replied 4 August 2017, 2:50 pm EST

    Does somebody from DD have an answer of the bug / difference in behavior with landscape between version 2.0.1195 and 2.4.1279?



    That would help us finding a solution for our customer.



    Ingar.


  • Replied 4 August 2017, 2:50 pm EST



    Are you able to post what code you are using to set the
    orientation, paper size, etc 



    The reason I mention margins earlier is that if a printer requires certain
    specifications, say .51 inch margins, and the report is set to .5...

    ActiveReports will sense this is incompatible and change the settings to be
    default, which could account for the page orientation changing from what you
    specify.



    The way to test this is to try and print from WordPad with the same margins as
    your report.  If WordPad gives you an error and changes the margin
    settings, those margins cannot be used on that printer.



    Make sure when moving from 2.0.0.1195 to 2.4.0.1279 you upgraded all
    ActiveReports DLLs.



     

  • Replied 4 August 2017, 2:50 pm EST

    Here are some code from the RPX file  that we are loading:

        GUIDLIB="{00000000-0000-0000-0000-000000000000}" GUIDREP="{00000000-0000-0000-0000-000000000000}"
        LICENSE="10000000"
        PrintWidth="15000"
        DocumentName="GridPrint"
        ScriptLang="VBScript"
    >
            >


        RightMargin="850"
        TopMargin="850"
        BottomMargin="850"
        Orientation="2"
    >


    As you see the margins are large and should not make any trouble.
    All dll's are upgraded to 1279.  (arview2.ocx, arpro2.dll and all export filters.
    We also set the rendermode  (rpt.Printer.Rendermode = 1

    The customer tried a new printer, Canon IR 2800, and this resolved the problem.   But I still don't understand why the printer didn't work with the new arpro2.dll.
    Are there trouble with Canon and Active Reports?  (I posted a new thread about Canon and slow printing.)

    Ingar.

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels