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 print preview

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

    report print preview

    I searched existing messages and did not see what I need.
    Every time I preview a report, I have to resize it to see all of the data. Is there a way to save the view so it comes up full size (or at least the size that I need)?
    Thanks,
    Neil

    #2
    RE: report print preview

    My memory is that if you use a button on a form to print a report, and the form is maximized, the report will be maximized. The converse being that if the form is not maximized, the report will not be maximized.

    Seems as if you could handle maximizing the form from the same button as you print your report, then restore it to normal after, if you don't want the form maximized all the time.
    There can be only one.

    Comment


      #3
      RE: report print preview

      If you put
      this.maximize()
      in the OnPrintInit event of the report, it will always come up full screen. I don't believe there is any other way to specify a screen size.

      Finian
      Finian

      Comment


        #4
        RE: report print preview

        Thanks to Stan and Finian for their replies.
        Neil

        Comment


          #5
          RE: report print preview

          One thing to add.

          On the assumption that you start out with your form restored, then if you maximize the preview window on print_init after you print or cancel printing the calling form shows maximized. To correct this, attach

          this.restore()

          to the form's on_activate event.

          At least this is how I do it. The forms display restored and the print previews display maximixed and the user never has to touch either.

          Bill
          Bill Hanigsberg

          Comment


            #6
            RE: report print preview

            Guys:

            I think I have one better....

            On prin Init --- this.maximize()
            On Print exit -- this.restore()

            You don't have to fool with those commands on the buttons.

            Try it, I may be confused, but it's working on several reports that I use.

            Ken

            Comment


              #7
              RE: report print preview

              Whoa!

              Upon further testing........

              I should have know better than to try a 'one up' on Hanigsberg, the great Alpha GuRu.

              All right, the oninit and onexit print events as described above will work, but only if you use [ESC] to get rid of the preview screen. If you click on the system 'X' it won't restore the underlying form.

              You win again, Bill.

              Ken

              Comment


                #8
                RE: report print preview

                Whoa yourself ken!

                I'm no guru. Please.

                However, I came up with that recipe after a bit of trial and error that began with exactly the solution you proposed. I don't really remember the details but in general the problem was that there was more than one route to get back to the form and you had to intercept them all. It was simpler to just use on_activate code to restore the form since all roads led there anyway.

                There is so much to learn about this stuff and so much I have yet to touch. We're all students. That's what makes this board so collegial.

                Bill
                Bill Hanigsberg

                Comment

                Working...
                X