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

Dialog Filter help

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

  • Dialog Filter help

    I have tried looking through the various help guides and I know this is a simple problem to solve, but . . . it is driving me crazy.

    I have a dialog that is printing out a report which works fine. I now want to add in the dialog a user field (Hosp) to be a pretty simple filter that will limit the report based on the value the user types into this dialog's field.

    So the filter fires on the FormEvent AfterValidate as part of the dialog component:

    dim filter as C
    filter = (Hosp = patient->hospital)

    (I am showing what I am trying to accomplish - I know this is not even close on properly phrasing this filter.)

    "Hosp" is the dialog component and "patient->hospital" is the field in the table "patient" that I want to match up.

    So how do I phrase this? I know this is simple but I am missing it.

    Thanks,

    Mike Scholin

  • #2
    Re: Dialog Filter help

    I figured it out!

    filter = ("Hospital=\""+hosp+"\"")

    I have no idea as to why this works but it does.

    NOW, the other part of the filter that worked great by itself won't work together with the above using an ".and." join.

    Code:
    filter = "patient->date_of_service >= " + s_quote(ctod(from_date)) + " .and. patient->date_of_service <= " + s_quote(ctod(to_date)).and.("Hospital=\""+hosp+"\"")
    When this runs together I get:
    Errors in: event.AfterValidate code:
    Argument is incorrect data type

    What needs to be changed to make them run together?

    Thanks!

    Comment


    • #3
      Re: Dialog Filter help

      You need to include the final .and. in the final set of quotes with Hospital.
      Pat Bremkamp
      MindKicks Consulting

      Comment


      • #4
        Re: Dialog Filter help

        Compound filters are a pain. One helpful hint is to place save_to_file("c:\test.txt",filter) somewhere after you set the filter value and to comment out the code that causes the page to fail, so it won't fail.

        That way you will get your resolved filter expression written to test.txt and can view it for syntax errors.
        Steve Wood
        Join the ALPHA DEVELOPERS NETWORK
        There is no Cloud. It's just someone else's computer.
        Web - Mobile - Hosting - Products - Frameworks - Developer Resources
        AlphaToGo | IADN (100% Alpha Anywhere Websites)

        Comment


        • #5
          Re: Dialog Filter help

          Pat, I have tried several different configurations/combinations of quotes and slashes but with no success.

          Were you able to see specifically where I needed the quotes?

          As Steve confirmed (glad it just wasn't me only), these compound filters are a pain!

          Thanks, Mike

          Comment


          • #6
            Re: Dialog Filter help

            Its difficult to parse without your database to bounce against. Maybe this will help, here are several working filter expressions with lots of slashes and .and.'s.
            Code:
            ?str(tablecount("[PathAlias.ADB_Path]\tr_trust", "Customer_ID = " + quote(session.customer_id) + " .and. Online_Submit_Status <> .t."))
            
            ? str(tablecount("[PathAlias.ADB_Path]\tr_trust", "(Customer_id = \""+session.customer_id + chr(34) +  ".OR. Attorney_id = \""+session.customer_id + "\") .and. Received_Date > " + s_quote(date()-60)))
            
            varfilter = "date() - ctod(time(\"MM/dd/yyyy\",Regdate))= " + s_quote(dy) + ".and. regstatus ="+s_quote(rs)
            
            record_delete("datapath\web_users","regstatus = 'pending' .and. date() > regdate + "+expdays)
            Steve Wood
            Join the ALPHA DEVELOPERS NETWORK
            There is no Cloud. It's just someone else's computer.
            Web - Mobile - Hosting - Products - Frameworks - Developer Resources
            AlphaToGo | IADN (100% Alpha Anywhere Websites)

            Comment


            • #7
              Re: Dialog Filter help

              Thanks Steve! I love good examples - I have figured more things out with sample code than through any other source.

              I guess it is not the same but it sure would be nice if you could build these filters like you do in alpha expressions (grids) and then see the translation that would work for xbasic.

              Thanks again for your help.

              Comment


              • #8
                Re: Dialog Filter help

                Well, I got it working between Pat's suggestion and Steve's examples AND A whole LOT OF JUST PLUGGING IN A LOT OF QUOTES WITHOUT ANY UNDERSTANDING WHY!!!

                Code:
                filter =" Hospital=\""+hosp+"\"" ".and. ""patient->date_of_service >= " + s_quote(ctod(from_date)) + " .and. patient->date_of_service <= " + s_quote(ctod(to_date))
                It all works great now and will be a big boost to my application, but I do wish I could understand why it is working!!
                Steve, you are so correct that these compound filters are a pain!

                Thank you guys for helping.

                Comment

                Working...
                X