Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Report not allowing A3 Landscape

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Report not allowing A3 Landscape

    Hi,

    I am new to reports, and am using the latest pre-release build.

    When I set the report to A3 (similar to 11x17 in size) "Landscape", the report remains in "Portrait" orientation.

    In fact, I can't seem to get "Landscape" mode to work at all, no matter the paper size. Whenever I do a preview, I still see the report as "Portrait".

    Any idea if this is a bug, or whether I am doing something wrong? Does it work for anyone else?

    Thanks,
    Andy.

    #2
    Re: Report not allowing A3 Landscape

    Are you designing the report in 11 x 17 landscape? The report will always have the format that it was designed with. I have to design reports for different output formats 1 for portrait and 1 for landscape.
    Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

    Comment


      #3
      Re: Report not allowing A3 Landscape

      Hi Frank,
      I think I figured it. I had to define the page size and orientation in the Quick Report Genie BEFORE continuing to Layout Report. Once in the Report builder, any changes I try to make to orientation do not take. This is a quirk that I hope can be fixed by Alpha, unless I am missing something.
      Andy.

      Comment


        #4
        Re: Report not allowing A3 Landscape

        Nope - not figured yet. By doing as I stated above, the page setup is correctly defined as A3 landscape, and it previews as an A3 landscape page in shape and size. However, the main editor does not allow you to access beyond a width of 10.6 inches or so - i.e. portrait width. Therefore, you can't place fields on the entire landscape canvas. There must be a bug in there, if I am not mistaken!

        Comment


          #5
          Re: Report not allowing A3 Landscape

          When I get back later I will give it a try and see if I have the same issue.
          Last edited by frankbicknell; 07-07-2012, 09:22 AM.
          Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

          Comment


            #6
            Re: Report not allowing A3 Landscape

            I have the same issue.
            Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

            Comment


              #7
              Re: Report not allowing A3 Landscape

              Update - I was able to eventually get the page set to A3 landscape. Let me rephrase - eventually I got luck and it "stuck". But it still wouldn't display as such from the Web. Then, out of interest, I tried changing up the report and setting it back to portrait and again it wouldn't change back! I ended up recreating the report again. There are definitely bugs in there that are preventing the orientation from saving. I do hope Alpha addresses these.

              Comment


                #8
                Re: Report not allowing A3 Landscape

                Does the choice of the default printer affect the symptoms?
                Al Buchholz
                Bookwood Systems, LTD
                Weekly QReportBuilder Webinars Thursday 1 pm CST

                Occam's Razor - KISS
                Normalize till it hurts - De-normalize till it works.
                Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                When we triage a problem it is much easier to read sample systems than to read a mind.
                "Make it as simple as possible, but not simpler."
                Albert Einstein

                http://www.iadn.com/images/media/iadn_member.png

                Comment


                  #9
                  Re: Report not allowing A3 Landscape

                  Hi Andy
                  I had the same problem (with a different page size) and like you, eventually got it to stick. The choice of default printer definitely wasn't the problem - I always picked the same one
                  Now I'm afraid to edit because it 'works'!
                  Garry

                  Comment


                    #10
                    Re: Report not allowing A3 Landscape

                    UPDATE: I got it working now. Despite selecting my preferred page size and orientation in the Genie, it is important in some cases to edit the report properties, reselect the right page and orientation, and force it. Then it behaves better. When the page size was displaying "custom", I was having problems making things stick. Also, different printer drivers behave differently, so try a few.

                    Comment

                    Working...
                    X