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

Filtering Letters/Labels for Unique Records

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

    Filtering Letters/Labels for Unique Records

    I have created an envelope that prints addresses based on a query of marked records. In the table several records that have an identical value in the NAME field may be marked.

    When I attempt to query the records using an operation that sorts by Name, queries the marked records, and checks that each record is unique, the query comes back correct. However when I print the envelopes (basing the order and filter on the current selection of records), I end up with multiple copies of the same envelope.

    If I set the envelopes to Prompt for Criteria at Print time, I can check the box next to Unique Records, and everything will print correctly without duplicate envelopes.

    I really just want to set a filter parameter to force it to use unique records that are marked.

    #2
    RE: Filtering Letters/Labels for Unique Records

    when you say "the query comes back correct", if you display a browse of the results of the query, do you see only one instance of each name? is that what you are saying?

    Comment


      #3
      RE: Filtering Letters/Labels for Unique Records

      Thats right. A browse instance of the query shows one unique instance of each name, yet the record selection for printing ignores and treats the current selection of records as if the unique flag were not in place.

      Comment


        #4
        RE: Filtering Letters/Labels for Unique Records


        Chris,

        There may reasons for not doing so, but have you considered unmarking all the records, running the query to find unique entries, marking them, and then just printing the marked entries? It's an extra step or two, but...

        -- tom

        Comment


          #5
          RE: Filtering Letters/Labels for Unique Records


          Chris,

          Is your envelope layout based on the same table as the table against which your query is being run?

          -- tom

          Comment


            #6
            RE: Filtering Letters/Labels for Unique Records

            The envelope layout IS based on the same table as the query.

            I am not able to go through the process of unmarking all records, querying unique names and then marking them. There is another report that is generated that need to have all the marked records, even the duplicates. The report prints first, then envelopes print for each addressee.

            Comment


              #7
              RE: Filtering Letters/Labels for Unique Records


              Chris,

              Your problem is very curious. Any chance you can post a working model here so we can look at the details?

              -- tom

              Comment


                #8
                RE: Filtering Letters/Labels for Unique Records

                I am attaching a copy of the database.

                The process that would normally occur is a person would go through and mark all records that need to be marked. Then run the PID Marked A query. Then print the Affidavit of Mailing Report. Then Print the PID Envelope A letter. Then run PID Marked B query. Then Print the PID Envelope B letter.

                Comment


                  #9
                  RE: Filtering Letters/Labels for Unique Records

                  Chris,

                  Thanks. I was able to duplicate the problem here, and did not see a quick fix. Will look further tonight, if the creek doesn't rise too high!

                  Have you thought about using a report, instead of a letter layout? I recall others who have hit limitations of the letter engine that do not seem to be present with the report engine. Maybe a properly formatted report can be used to crank out your envelopes for you?

                  -- tom

                  Comment


                    #10
                    RE: Filtering Letters/Labels for Unique Records

                    Chris,

                    Here's a solution to your dilemma, but no explanation for why it was happening in the first place.

                    Run PID Marked B query;
                    Then print / preview TstReport.

                    Design notes in the report layout explain what's going on.

                    Let me know if you have questions.

                    -- tom

                    Note to lurkers: Solution involved using a report with a group break, suppressing the report details band, and using the group header band, formatted as a #10 envelope. Report begins new page each time the group breaks. The effect is to get one envelope for each group. I broke the group on the Names field, so you get one envelope for each "Name" in the currently selected records, regardless of how many times that name may be repeated in succession. You can't do this kind of thing in the letter layout because I don't believe it supports group breaks.

                    Comment


                      #11
                      RE: Filtering Letters/Labels for Unique Records


                      Ok, time to refill the coffee cup.

                      Here's the file.

                      Unzip it to a separate folder. Do not mix with your development work.

                      -- tom

                      Comment


                        #12
                        RE: Filtering Letters/Labels for Unique Records

                        in version 5 you can use a new function
                        key_unique_value() in a filter expression to return just unique records.
                        key_unique_value() is a special function that returns .t., but internally turns on the unique flag. it is useful in situations where a5 is asking for a filter, but not filter flags.

                        for example, say you want to print a report.
                        the report.print() method syntax is

                        report.print("reportname","filter","order")

                        so, you might write

                        report.print("labels","overdue>30 .and. key_unique_value()", "lastname")

                        this would only print one record for each lastname.

                        Comment


                          #13
                          RE: Filtering Letters/Labels for Unique Records

                          Thanks Tom! This worked.

                          Comment

                          Working...
                          X