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

Printing bug (con't)

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

    Printing bug (con't)

    I note that earlier there was a mention of a printing bug that someone discovered in 4.5. I've been seeing something similar since very early in Version 4.

    I've attached a reduced verison of a database that demonstrates this. This is a database used to keep track of department policy documents. The one report included shows the problem at the bottom of page 4 and the top of page 5. The text "Separation from Employment" is the name of a policy numbered 60-70. The title appears at the bottom of page 4 while the balance of the record appears on page 5.

    I've played with this a good bit to see what the driving issue is. I've managed to avoid the bug by fiddling with the height of the detail record. However, each time the report is run, I have to check to see if the bug shows up and if so, by trial and error move the detail record height to get it to go away. This isn't a useful solution.

    Eric Johnson

    #2
    RE: Printing bug (con't)

    I forgot to mention there's a second manifestation of this problem....this or a closely related one....at the bottom of page 2 and the top of page 3. The title is split over the 2 pages although the report design calls for records to be kept together on a page.

    Eric Johnson

    Comment


      #3
      RE: Printing bug (con't)

      Try unchecking the 'repeats on page/group break' property of the group's header settings.

      Using vers. 4.03 build 230 this seemed to print just fine.

      Comment


        #4
        RE: Printing bug (con't)

        Well.....I wonder why I had that set.

        Anyway, good news and bad news. I removed that and indeed in the sample I sent, the problem went away. Then I went to the real database and made the change and the problem went away. Then I reduced the size of the detail section slightly to tighten the report composition a bit. Bang! The problem re-occurred. Then I went to the sample I'd posted here and got the same result.

        Thanks but it appears the problem just isn't that simple. I do woner why I had that option set however.

        Eric

        Comment


          #5
          RE: Printing bug (con't)

          Eric, I wonder if your tightening the detail section is what's causing the problem. If I were you, and the report ran fine with just a tad more white space between lines in the detail section, I'd accept the layout... on the theory that my head would stop hurting as soon as I put the hammer back in the toolbox.

          My guess is that when Alpha Five calculates remaining space at the bottom of the page it must take a number of things into consideration, including font size and type, line height, page size, top and bottom margins, footers, headers, and a host of other things including the amount of 'white space' specified in the detail band in your report layout. In my book close enough is good enough. I don't expect my database engine to have the capabilities of a desktop publishing program. If I needed closer tolerances I'd probably export the data and do the report using other tools.

          Comment


            #6
            RE: Printing bug (con't)

            Tom-

            I understand what you are saying and don't necessarily disagree. However, the history of this thing is that as the report data varies, the problem comes and goes. There doesn't appear to be any single setting of the detail section that makes it disappear for good. That kind of unpredictability makes a work-around difficult to live with.

            Eric

            Comment


              #7
              RE: Printing bug (con't)

              Eric, I suggest you increase the white space (vertical height) in the detail band (region) a bit. Also it's important that the vertical height of the field object be tall enough to contain the text you are trying to print, considering font size and type. Since the text changes from record to record this can be a bit tricky, but should settle down pretty quickly. Add a bit of vertical room here too if you continue to have problems.

              Comment

              Working...
              X