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

Quick filter nets different results

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

    Quick filter nets different results

    I am modifying the sample mailing list app for a birthday card printing project. One of the options with the sample app allows the user to "View/Print/Export Mailing List". Choosing this option I can print labels and letters based on a mailing list choice. The user selects a "mailing list" record from an embedded browse on the form and then presses the "quick filter" button on the top toolbar. The filter does its' job and the user can view the filtered results by pressing a button to bring up a browse window.

    Here is the weird thing.

    On this form there are two buttons. one to output labels and another to output letters using the standard :letter.print("lettername") and :label.print("labelname") syntax.

    In the properties menu of both the label and the letter files, under the "records" tab I have set filter expression to "all" and "Additional Record Order and Filter Criteria" to "Base report on current selection of records"

    When I print the letters all the correct letters print out. But when I print the labels I get completely different output. I get the correct number of records but they don't match the desired filtered output.

    I tried to set the "Additional Record Order and Filter Criteria" to "None" but it only gave me one correct record and no more, the correct answer is 12 records.

    #2
    RE: Quick filter nets different results

    This will be easier to troubleshoot if you post a working model of your database, with instructions on which form and buttons you're describing.

    -- tom

    Comment


      #3
      RE: Quick filter nets different results

      Greg,

      A quick look at the sample here indicates that the sample itself may not be working correctly. I didn't see anything that filtered the records based on the currently selected mailing list when the labels or reports are run. However, it's been years since I last looked at this and it's possible I am no longer looking at the actual sample that shipped from Alpha. (I've been known to change them ... sometimes on purpose... more often by accident!).

      For the reports and labels to run you need to either:

      1) set additional filtering criteria in the layout design to NONE, and then pass the filter to the layout in the preview() or print() command; or

      2) leave additional filterin criteria set to 'use currently selected records' and run a query based on the current mail list selection BEFORE calling the report or labels.

      -- tom

      Comment


        #4
        RE: Quick filter nets different results

        Here are the files! This issue is driving me around the bend!

        Comment


          #5
          RE: Quick filter nets different results

          Greg,

          The properties of the label layout are defined for the wrong table in the set.

          Open the 'bdaylable' label layout in design mode. (Yes, I know it's misspelled, but spell it wrong anyhow).

          Choose:
          Properties, then
          Label Tab.

          Now set the Table level to: People_Info.

          Then choose:
          Records Tab, then
          set 'Additional Filter Criteria' to
          'Base report on current selection of records'.

          Save it.

          I think you will find that it behaves correctly now.

          The labels need to be pulled from one of the child tables in the current set.

          It took me a while to see this, so don't feel badly. Most of my work with labels has been with single tables, not sets of tables.

          Let me know how it works out...

          -- tom

          Comment


            #6
            RE: Quick filter nets different results

            You were right on the money again Tom! It is amazing how it could be just under my nose. My problem was that I was using the letter properties as my guide. I didn't see any reference to the correct table in the set. How did you figure out which table to use? Or was it just trial and error?

            Comment


              #7
              RE: Quick filter nets different results

              Greg,

              Yes, in a manner of speaking.

              I saw right away that the Avery 5161 label layout behaved correctly. So I compared its properties to that of the misbehaving label layout. It took a while. Then I realized I didn't know the purpose, really, of the "table level" entry in the label layout properties dialog. I noticed that in the Avery 5161 layout that the layout was based on the same set, but that the layout's 'table level' specified a child table, not the primary table of the set. When I went back to bdaylables I saw that in the misbehaving layout the primary table was specified, instead.

              The rest was easy.

              -- tom

              Comment


                #8
                RE: Quick filter nets different results

                Many thanks once again Tom.

                Comment

                Working...
                X