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

Excluding duplicate records in summary

  • Filter
  • Time
  • Show
Clear All
new posts

  • Excluding duplicate records in summary

    There has to be an easy solution to this, but for some reason it's eluding me.

    I want to create a report which has a list of names and phone numbers, in two different groups. At the bottom of each group I want to place the total number of records within the group. However, some of the records have duplicate phone numbers, because they are in the same household. I would like the number which shows the total to reflect the number of households, not the number of records. How do I exclude the duplicate records from the total number?


  • #2
    RE: Excluding duplicate records in summary


    I'm doing this from what little memory I have so it may not be quite accurate but will get you going. Go to the Operations tab and create a Find Duplicates or Duplicate operation based on the phone numbers. Then when you create the report, exclude the marked records in the report's Detail Properties filter.

    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.


    • #3
      RE: Excluding duplicate records in summary


      Perhaps you could create a calc field that evaluates to 1 when the current phone number does not match the previous ... Then you could print the total using a new calc / summary field generated by the genie, totalling all the calc fields in your group.

      If the phone number field were called 'PhoneNum', something like this is what I have in mind:

      if(trim(PhoneNum) trim(Previous("PhoneNum"), 1, 0)

      This approach would require you to sort the records in order such that the dupe phonenumbers fall one right after the other...

      -- tom


      • #4
        RE: Excluding duplicate records in summary

        Thanks for the tip, but the report actually is based on a filter that only uses a small part of the table. Not only that, but I want the duplicate records to be listed in the report. I just don't want them included in the "total" number shown at the bottom.



        • #5
          RE: Excluding duplicate records in summary


          That's a great idea, but I really don't want to sort them by phone number. Is there a way to use the sort in the expression which returns the total, but displaying the records in Lastname + Firstname order?



          • #6
            RE: Excluding duplicate records in summary

            Nathan, nope. I don't think so.

            Give your requirements you may need to make multiple passes through the table to compute the total phones you want to display in the report; store the result in global variables; display them in the report.

            -- tom


            • #7
              RE: Excluding duplicate records in summary


              Your specification is the number of households, or is it phone numbers? Let me assume this is by household. How many households do you have with two private numbers being given? What if you have a cell phone number for one party at the same home? I see you already have multiple users at some houses in your data.

              As you can see, perhaps your set or filter designs need to reflect your business model more closely. You may want to filter on the basis of home address if that is your prefered method. The other option is to adjust your tables and sets so that households are a table and users are a one to many linked child table. This will make it much easier to manage your reports with respect to households and individuals.



              • #8
                RE: Excluding duplicate records in summary

                Create a calculated field for whatever defines a "household" (e.g., "addr1 + addr2 + zip") for the report. This field does not have to appear on the report. Base your summary on this field.


                • #9
                  RE: Excluding duplicate records in summary


                  Thanks a lot for your tip! I have a code field in the table which I have marked "N" if it's a duplicate address. Using your suggestion, I created a calculated field called "household" on the report that evaluated to 0 if it was marked "N", otherwise 1. Then I created a summary field which added the numbers in the "household" field, which gives the correct number. Thanks again!