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

Query filter help needed

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

  • Query filter help needed

    My table has username and datepaid fields. There are multiple usernames, ie, same are repeated possibly several times for each datepaid. What I need to do is extract the last date paid for each username in the table. I would like to do this via either an index or a query, preferrably, then display the records in a browse. It seems quite simple, but it eludes me. Any help would be appreciated.

    Tom Lyon

  • #2
    RE: Query filter help needed

    Tom,

    If username is truly unique and datepaid is a date field you could query on username+cdate(datepaid) and fetch the last record.

    If there are a lot of records you could build an index so the query optimizes.

    Bill
    Bill Hanigsberg

    Comment


    • #3
      RE: Query filter help needed

      "...and fetch the last record..."

      I must be dense. I didn't see how you got there. Could you explain? I'm looking for the last datepaid for each unique username in the table.

      Tom Lyon

      Comment


      • #4
        RE: Query filter help needed

        I think you could make an index on username+invert(cdate(datepaid)) with a filter Dbmax or maximum or tablemax. I haven't read up on these or tried it but it would seem that you could use one of them to only include the greatest date paid for each username.

        I was thinking another way might be to do a query with the above order and then run a query on the query results to filter out lesser dates.



        Russ

        Comment


        • #5
          RE: Query filter help needed

          No promises here, but try this.

          Link the table to itself - one to one (last match)
          parent linking field - name
          child linking field - cdate(datepaid)

          Create a browse on the set.

          Run a query on the top level table, order my name, use the unique option (or use a unique index on username).

          query:
          f = browse.load("mybrowse")
          t.f:tables:usernames.this
          query.options = "u"
          query.order = "usernames"
          query.filter = ""
          t.query_create()
          f.resynch()
          f.show()
          f.activate()

          If you create a index, just display the browse. I'm not a 100% on this, but it seems like it should work.

          Comment


          • #6
            RE: Query filter help needed

            Here's another option with minimal xbasic.
            create a dummy table with one field username
            append all unique usernames from your table
            link dummy to your table one to one, first matching.
            sort your table on username+invert(cdate(datepaid))
            It should then only display the newest date record for each user.
            The only thing is you will have to put an append unique to dummy operation on the save of the form used to enter username to keep the dummy up to date.

            Now on a form for the set display an embedded browse, it should only have the records you want.

            Russ

            Comment


            • #7
              RE: Query filter help needed

              Hmm.

              I'm not following your logic at all, and as such, am unable to implement what you suggest. I can be rather dense at times and I bet this is one of those times :) I did try to follow your ideas, but get similar results to what I have been seeing. I know there is a way to do this...

              Tom Lyon

              Comment


              • #8
                RE: Query filter help needed

                Clarification: previous message referenced Steve's post, not Russ'. I've yet to try Russ' suggestions.

                Tom Lyon

                Comment


                • #9
                  RE: Query filter help needed


                  Tom,

                  Here's one solution, using a script to mark the last payment records, and then running a query to display only marked records.

                  -- tom

                  Comment


                  • #10
                    RE: Query filter help needed

                    See zip

                    Comment


                    • #11
                      RE: Query filter help needed

                      I still don't follow, Steve.

                      I am looking for, based on your sample data, 7 records out of the 20 records in payments to be displayed in the form named lastpaid. I see 20 records there as well. Was this your intention?

                      If this method can work, it will be slick.

                      Tom Lyon

                      Comment


                      • #12
                        RE: Query filter help needed

                        That was my next step, too. You've worked it out nicely, and it works well. I was really hoping for a simpler solution, but we'll work with what we have to and get the job done.

                        Really appreciate your hard work in this and all the issues to which you contribute.

                        Tom Lyon

                        Comment


                        • #13
                          RE: Query filter help needed

                          My form only displays the seven records from the DB I created. I just downloaded my own zip and it, too, only displays seven records. Perhaps someone else might try downloading the zip and see what they get. Can't explain your results.

                          Comment


                          • #14
                            RE: Query filter help needed

                            My form only displays the seven records from the DB I created. I just downloaded my own zip and it, too, only displays seven records. Perhaps someone else might try downloading the zip and see what they get. Can't explain your results.
                            ----------------------------------------
                            Yes, I can. You're using the wrong index when displaying the form "Lastpaid." Select the index, "Userpaid" by hitting control-I and choosing from the dropdown.

                            Comment


                            • #15
                              RE: Query filter help needed

                              You are correct! Very cool!

                              Nice work, Steve. Very good insight.

                              Tom Lyon

                              Comment

                              Working...
                              X