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

Running Count Break on Report

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

  • Running Count Break on Report

    I have a running count on a report that works find and puts a number next to each detail.
    Two issues - I am trying to only print record where running count is <= 101, but it ignores the filter.

    Second I really wanted to Break every 10 records and put a statement inbetween. My thought was to do subreports with each one filtering on records from 1-10, 11-20 etc. But when I do this, its blank.

    Any other thoughts on how to do this.

  • #2
    Re: Running Count Break on Report

    Hi Leah,

    So you only want to print the first 100 records in the table and you want to break them into blocks of 10. Or is there a filter on the report first?
    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: Running Count Break on Report

      Leah,
      You would think that this would be an easy thing to do...but most times it is not.

      Unless I have missed something that someone else has gotten to work (the mod(mrec())......does work but for very few situations--HAS to be in detail section I believe.), try using the brute force method...

      Expand your header and footer that surrounds your detail section until the amount of records that can be shown is the number you want to see (10).


      EDIT: here are two samples I gleaned from the messageboard---they actually could be the same ones....or similar at least it looks like. I think they both use the mrec() method.



      Limit_Records--Report-Tom.zip
      Mike
      __________________________________________
      It is only when we forget all our learning that we begin to know.
      It's not what you look at that matters, it's what you see.
      Henry David Thoreau
      __________________________________________



      Comment


      • #4
        Re: Running Count Break on Report

        Another solution here would be to copy the records to a new temporary table and base the report on that table. Each new record in that table would receive a grouping id number, so that each block of X records would have the same grouping id. Once the report has been run the temp table would be emptied.

        Comment


        • #5
          Re: Running Count Break on Report

          Originally posted by Leah View Post
          I have a running count on a report that works find and puts a number next to each detail.
          Two issues - I am trying to only print record where running count is <= 101, but it ignores the filter.
          Are you saying you are using run_count() in the filter?
          That would be an egg/chicken scenario, wouldn't it?

          The run_count is constructed AFTER the table has been filtered and tallied and thus and therefore and by virtue of which you will ALWAYS have running count starting at 1 onward. It is not ignoring anything. You cannot use run_count() in a filter. I haven't even tried, but I don't think it will work or yield anything, assuming I am understanding your question correctly.

          Perhaps what you need is to execlude the first 100 records using either top_records() or bottom_records() or one of those functions.

          Comment


          • #6
            Re: Running Count Break on Report

            I am going to try a combination of your suggestions this weekend.

            Thanks for the tips - I had a feeling by what I was seeing that I would have to create a temp table of some sort.

            Comment

            Working...
            X