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
Devcon 2020 Goes Virtual! LEARN MORE >

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 Headaches

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Report Headaches

    I have an invoice report that has the following components
    1) Page header for report"
    2) Report Header
    3) repeating detail header
    4) detail
    5) repeating detail footer
    6) report footer

    The page header for report holds the company's letterhead, client addresses, ship to and billing info etc. I put it here because I want this to print on every page.

    The report header contains an invoice notes field that only prints on the first page of the invoice just above the repeating detail header.

    The repeating detail header holds field titles like quantity, description and price etc

    The detail well, it holds record details. Shrink contents of band is checked

    the repeating detail footer is empty

    The report footer holds the invoice totals and this prints once at the end of the report. Justify to bottom and keep region together is checked.

    I have a number problems and my research on this site has not yielded any clues. First, I find that when there are more than 5 detail items, the report footer jumps to a second page as if it were being forced there by a bunch of invisible records. If there are 34 detail items I would find that the first page will hold all 30 items and the second page will have 4 items and the report footer will appear as expected on the bottom. The problem is that the item average is 10 to 20 items and there seems to be enough space on the first page to hold at least 18 items along with the report footer. What am I doing wrong?
    Tags: None
    #2
    RE: Report Headaches

    Greg,

    I'd investigate the differences if:

    1) the repeating detail footer were removed from the layout; and

    2) instead of a repeating detail header, you insert a group break, and use the group header band for your column heading text labels.

    -- tom

    Comment

      #3
      RE: Report Headaches

      Greg,

      I'd also put the invoice totals in the group footer band, instead of the report footer.

      -- tom

      Comment

        #4
        RE: Report Headaches

        I'll try your suggestions, I never thought to put things in the grouping level since there are no groups needed for this report.

        I came across a semi solution if you can call it that. During the creation of these reports I discovered a strange property associated with one field. Generally, in my detail band fields I put a establish a right/dash as a border property to visually separate field items. One field in the detail band was printing this vertical dashed line when data was present in the field and nothing when there was no data. It made the form look bad. I couldn't get anything to work so I fabricated a little vertical dotted line with the line tool and placed it at the right end of the field. When I removed this little line the problem outlined above disappeared. I needed the line so I thought that it may have something to do with the length of the line so I made it shorter than the height of the field and the problem reappeared but I got my line. So I have decided to do without the line even though I know what the client will say.

        Another interesting thing is that I have a comment field with a character length of 100 in each detail record. My hope was that if needed I could have a comment written for detail items that warranted a comment. But I wanted to give the field the ability to grow. I didn't want to use a note field type so I opted to put a RTF field into the detail band and then insert the character field into that in order to have the ability to grow. Well as it turns out, the report doesn't like that either the result is the report headache problem. When I removed the RTF field the report seemed to print normally.

        Comment

          #5
          RE: Report Headaches

          Greg,

          Have a look at your report and see if there are any elements out of place. These can force Alpha to go to a custom page size which might give you some of the symptoms you are experiencing. You'll have to watch that your report segments all add up to the correct page size in length and width.

          Another footer option would be to use the page footer specification. This way you know where the bottom of the page is falling. If your page setup is to have record grouping for four records checked and keep footer together on a page checked, then at the least amount of page oversize beyond 11" you will get the entire footer and four records printed on the next page. This is what you asked Alpha to do...

          Your Rich text fields will work, but they need to have enough area in the box so the font can fit multiple lines in the box.
          - Dave

          Comment

          Previous template Next
          Working...
          X