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 Page Break Dynamic Property

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

  • MoGrace
    replied
    Re: Report Page Break Dynamic Property

    Thanks Stan, it gives me something else to look into.

    Leave a comment:


  • Stan Mathews
    replied
    Re: Report Page Break Dynamic Property

    Haven't had a chance to follow up here. I was never fond of sub reports and most folks that tried to use them, that I encountered, were trying to do so not according to the documentation.

    Not saying you are because I haven't looked. I may have time over the holiday to check it out.

    Table.external_record.....() or *collect() are the tools to build the string.

    Leave a comment:


  • MoGrace
    replied
    Re: Report Page Break Dynamic Property

    No bites yet? I can get the number of records for Tag_Nos in the detail section to show ok, but then the the other sub report of 1:N records shows nothing.

    Maybe I could try getting the Yarn_Split records into a string...and display that in the header instead of using the table.

    Stan - any thoughts on that? Maybe in an On Record event for the group?

    Leave a comment:


  • MoGrace
    replied
    Re: Report Page Break Dynamic Property

    If anyone would like to play with this report, I included the files.

    Knit Control is the original report that works fine as it is.
    Lot Control is my current attempt to limit the records per page. It has some problems with the 2 subreports in the detail section not showing together on the 1st page.
    TestLotCtrl is merely another attempt at the report. Problems include blank pages and the yarn_split subreport showing on only the last page for the Sch_No group instead of all the pages

    LotCtrl.zip.

    Leave a comment:


  • Stan Mathews
    replied
    Re: Report Page Break Dynamic Property

    It has been a long time since I created a report but conceptually, a report with a known height page header and footer, no other headers or footers, can have the detail band height adjusted to create a known number of lines per page.

    If you accomplish that you may have a starting point for your desired end result.

    Leave a comment:


  • MoGrace
    replied
    Re: Report Page Break Dynamic Property

    I am trying to print out a Lot Control that prints out only the tickets for the number of pieces in each lot per page. A variable will be set for this number, but the report should print out pages for the total pieces for the machine scheduled. Ex: 84 pieces are to be produced on a particular machine grouped in lots of 20 rolls each.

    I created a group break for the detail section with the expression int(mrecno()/20-.01). This works to limit the subreport detail section to 20 records on the 2nd and 3rd page and the remaining 4 records on the 4th page. Almost perfect - except the very 1st page shows only the main group header with no detail -basically a blank page.

    What other settings should I try?

    Leave a comment:


  • MoGrace
    replied
    Re: Report Page Break Dynamic Property

    If it was resolved in the old days then I ought to be able to find it! Closest I came was a post by Martin Cole but he never said HOW he did it...

    Leave a comment:


  • Stan Mathews
    replied
    Re: Report Page Break Dynamic Property

    Same number of records on each page? Seems we did that "in the old days" with a large footer.

    Leave a comment:


  • MoGrace
    started a topic Report Page Break Dynamic Property

    Report Page Break Dynamic Property

    Has anyone tried making a page break in a report respond to a condition set in its Enabled dynamic property? I thought this might be a way to paginate a report based on a run_count calc. But of course I couldn't get it to work.

    I have read quite a few posts about using mrecno() for this but have not got that to work either. Many of those threads are very old, so was wondering if anyone has been able to limit the records in the detail section of a report whether using a subreport or not? I would like to take a report and make it break over several pages with a limited number of records in each page.
Working...
X