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



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

Summary for the values in a field at end of report

  • Filter
  • Time
  • Show
Clear All
new posts

  • Summary for the values in a field at end of report

    Hi, I have a dilema and am not sure if I'm going about the solution the correct way. I've got a database that tracks clients and the types of Tax Organizers they receive. The field "Orgtype" has one of four values in it - "P", "A", "E", or "" (blank). I would like four rows to print at the bottom of the report, each row corresponding to one of the four values, i.e.:

    Paper =
    PDF =
    Electronic =
    No Org =

    I would like to get a count of each, but can't figure out how to do it. I really don't want to break the report up and group each section separately to get totals for each group (though that seems easiest), I just want totals at the bottom of the report.

    Any suggestions or direction that will set me straight would be greatly appreciated.

  • #2
    Re: Summary for the values in a field at end of report

    subreport at the report footer

    group/sort on the Orgtype

    subreport footer at Orgtype with the count.
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.
    "Make it as simple as possible, but not simpler."
    Albert Einstein


    • #3
      Re: Summary for the values in a field at end of report

      You could also create four calculated fields

      pcount = tablecount("yourtablenameinquotes","orgtype = 'P' ")
      account = tablecount("yourtablenameinquotes","orgtype = 'A' ")
      ecount = tablecount("yourtablenameinquotes","orgtype = 'E' ")
      blankcount = tablecount("yourtablenameinquotes","alltrim(orgtype) = ' ' ")
      Last edited by Al Buchholz; 12-03-2015, 06:16 PM.
      There can be only one.


      • #4
        Re: Summary for the values in a field at end of report

        Thanks to both for the responses... I haven't played around much with sub-reports, and Stan, your solution sounds like something more in my wheel house, so I'll give it a try and post my results...


        • #5
          Re: Summary for the values in a field at end of report

          Hi Stan,

          OK - So here are the calculated fields in the report I created, verbatim:

          pcount = tablecount("_1040.dbf","orgytype = 'P' ")
          acount = tablecount("_1040.dbf","orgytype = 'A' ")
          ecount = tablecount("_1040.dbf","orgytype = 'E' ")
          blnkcount = tablecount("_1040.dbf","alltrim(orgytype) = """)

          (in your original example, it looks like there was an extra " after the = that didn't belong - at least, I believe so, because I kept getting errors until I removed it).

          Anyway, i looked at the documentation for this function (never heard of it before, so once again thanks for opening my eyes), and it appears to do what I want. However, when I dropped these fields into the footer of the report, when I run it, the output is actually the name of the field, and not the calculated value... i.e., it just said 'pcount', 'acount', etc. Any ideas of what I'm doing wrong?

          Thanks again.


          • #6
            Re: Summary for the values in a field at end of report

            OK Stan - it works. A little Alpha weirdness? I went into each calculated field, deleted the entire function, re-typed it, and it worked. I can't explain it... but I can thank you... this is a *very* useful function, glad to learn it. Thanks!


            • #7
              Re: Summary for the values in a field at end of report

              Just looking at what you posted I think you should have a calculated field named Calc->pcount and the code inside it should be tablecount("_1040.dbf","orgytype = 'P' ")

              For blnkcount the code should be.
              tablecount("_1040.dbf","orgytype = '""'")
              Spacing that end part out for clarity it is ' "" ' "

              Last edited by preston2; 12-03-2015, 01:38 PM.


              • #8
                Re: Summary for the values in a field at end of report

                Hi, thanks for posting a reply... the following calculated fields work perfectly:

                pcount = tablecount("_1040","orgtype = 'P'")
                acount = tablecount("_1040","orgtype = 'A'")
                ecount = tablecount("_1040","orgtype = 'E'")
                blnkcount = tablecount("_1040","organizer <> .t.")

                I changed the calculated field for those not getting organizers (i.e. not paper, PDF or Electronic) from checking the orgtype field for a blank to simply checking the logical field 'organizer' that is a true or false. Everything else works great. And as I mentioned to Stan, this tablecount() function is a great one that I haven't used before, but plan on using extensively in the future - very handy.


                • #9
                  Re: Summary for the values in a field at end of report

                  Sorry for the typo. Using a laptop that wants pairs of quotes and I have to remove the second of the pair. I assume you explored the related functions tablesum(), dbcount(), dbsum(), etc?
                  There can be only one.


                  • #10
                    Re: Summary for the values in a field at end of report

                    I haven't yet, but rest assured - I WILL!