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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Multi-state button to filter a table

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Multi-state button to filter a table

    After searching the manual and this forum, I'm still unsure about filtering a table. I want a multi-state button to set a filter on a table prior to printing a report. As there's no display of records on screen, I simply want this to operate on the current table, rather than a form display. Is there a:

    tbl.filter(lastname="Smith")

    sort of function somewhere, and if so, why can't I find it? In the xbasic manual index there are only two entries starting "filter" and neither of these helps. I'm fairly sure I'm being stupid, for which I apologise in advance.

    Martin.
    Tags: None
    #2
    RE: Multi-state button to filter a table

    Martin

    What you are looking for is a query. If you look through the documentation and search the forum for queries with variables, you should get enough informnation to do what you want.

    Jerry

    Comment

      #3
      RE: Multi-state button to filter a table

      Martin, ch 13 of the xbasic Ref Manual may help, too.

      Code:
      :Report.preview("YourReportName" , "Lastname = 'smith' ")
      - tom

      Comment

        #4
        RE: Multi-state button to filter a table

        Many thanks, Jerry and Tom. The preview() option is perfect for whatI'm doing at the moment, Tom, and Jerry has reminded me about queries. Lifesavers, both.

        Comment

          #5
          RE: Multi-state button to filter a table

          Oh, dear! So near, yet, somehow, I can't quite get there!

          Look at this script, it's attached to a button on a small form. The form allows the user to select whether details of all clients or just those starting with a specific letter are printed. It's simpler than the CustomerBase form in the Invoicing sample app., (which I copied it from) as there is no browse, or, indeed, any client details shown at all. Just a multi-state button (containing A to Z choices), an "All Clients" button, and a "Print Preview" button (and a "Cancel" button).

          This code is attached to the "Print Preview" on-push:
          Code:
          ''xbasic
if ltr="1" .or. ltr=""
	:Report.preview("gstlist","","'lastname'+'firstname'")
else
	:Report.preview("gstlist","substr(guest->lastname,1,1)=VAR->ltr","'lastname'+'firstname'")
end if

ui_msg_box("TEST",VAR->ltr)

END
          If I've clicked either nothing (when ltr="") or the "Show All" button (which assigns ltr="1"), everything previews ok.

          Otherwise, the second :Report.preview line is run. This gives the message: "Error occurred parsing filter expression. ltr not found". However, the final test line is then run, displaying the value of ltr, showing the letter selected. I've copied the line:

          :Report.preview("gstlist","substr(guest->lastname,1,1)=VAR->ltr","'lastname'+'firstname'")

          and run it interactively, and it works fine, displaying just the clients starting with whatever letter I selected.

          I'm baffled. The value of ltr displays in my ui_msg_box() test, but isn't recognised in the Report.preview(). But it IS recognised if run interactively!

          I'm sure this is just syntax, but however hard I stare at the screen I just can't see what I'm doing wrong! Help.

          Martin.

          Comment

            #6
            RE: Multi-state button to filter a table

            Martin,

            Have you defined ltr to be a global variable.
            Try adding the following:

            dim global ltr as C
            ltr = parentform:ltr.value 'if ltr is present on the form

            you're close...

            Tom

            Comment

              #7
              RE: Multi-state button to filter a table

              No, makes no difference, I'm afraid, Tom. What I can't understand is how ltr is recognised (both in the first line of the script, and in my ui_msg_box() test, but not in the filter.

              I keep changing things around but, although all the evidence suggests that ltr is correctly set to whatever key is pressed in the multi-state button, it is not recognised in the report.preview parameters.

              I'm stumped!

              (Again).

              Comment

                #8
                RE: Multi-state button to filter a table

                At last! I don't know why (I'd welcome suggestions) but THIS works:

                Code:
                ''xbasic

fltr=ltr

if fltr="" .or. fltr="1"
	:Report.preview("gstlist","","'lastname'+'firstname'")
else
	:Report.preview("gstlist","upper(substr(guest->lastname,1,1))=VAR->fltr","'lastname'+'firstname'")
end if

END
                In other words, COPYING ltr TO ANOTHER (fltr) VARIABLE makes it work. It HAS to be a new variable.

                Beats me, but at least it works.

                Martin.

                Comment

                Previous template Next
                Working...
                X