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

Limit printed records in report

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

    Limit printed records in report

    I have a embedded browse that allows a user to select records to print. I then execute a script to print the "marked" records to a report.

    So far great. My problem is I want to limit the number of records printed on each page of the report to 4. I don't care if they print 60 pages, but each page must have only 4 records.

    Some one kindly point me as to where to start on this. I can't seem to find a way to define this on the report side so maybe it needs done on the form side at the print layout command?

    Thanks,

    Jeremy

    #2
    RE: Limit printed records in report

    Jeremy,

    I'm not sure how to do this, but my gut instinct is to have a count of the number of records and when the value gets to 4 then new page.

    Counting the number of records in a report is very straight forward so the number on a page would just as easy. You will need the use of a calculated field for this.

    If you know that each record will take the same number of lines on a page then design the report to fit the paper. Use extra blanks to pad the page if you need to.

    You may have to experiment a bit. Let us know how you get on.

    Regards

    Keith Hubert

    Guild Member
    London.
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    Comment


      #3
      RE: Limit printed records in report

      I think you will have to achieve this by defining a group based on an expression.

      If you number your records as Keith suggests you can create a grouping expression like
      mod(calculated_record_no,4)=0
      which will become true every forth record

      There is a setting in group properties to start each new group on a new page.

      Bill

      Does someone have a simpler way?
      Bill Hanigsberg

      Comment


        #4
        RE: Limit printed records in report

        Bill,

        the need for a grouping expression is paramount. You could do it by inserting a new field in the table structure, and then fetching through the selected records, the field value of the first 4 recs would be 1, the next 4 would be 2, and so on.

        If doing violence to the current structure is not an option, you could achieve the same result by copying the field values from the selected records to a new table, which included such a 'grouping' field. the report could be based on the new table, and grouped on the grouping field. This table would be zapped after each successful print run, and then repopulated once the user selects the next bunch of records to report.

        -- tom

        Comment


          #5
          RE: Limit printed records in report

          Hi Tom,

          I understand that we need a group based on some record numbering scheme--indeed, that is what I suggested.

          But if I take your point correctly, you are saying that this number cannot be calculated on the fly and must exist in the data source for the report, the original table or a temp table if need be.

          Correct?

          Bill
          Bill Hanigsberg

          Comment


            #6
            RE: Limit printed records in report

            Yes, that's been my experience. If anyone else can suggest an alternative I'd be very interested in seeing it.

            -- tom

            Comment


              #7
              RE: Limit printed records in report

              In the first instance it may prove easier for Jeremy to follow up on Keith's second suggestion to adjust the height of the detail section so that the printed page will only accept 4 records. This assumes of course that there are a fixed number of printed lines per record, with no memo fields containing "essays"

              Comment


                #8
                RE: Limit printed records in report

                Agreed!

                -- tom

                Comment

                Working...
                X