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



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

object properties in filter expressions

  • Filter
  • Time
  • Show
Clear All
new posts

  • object properties in filter expressions

    I am creating a report and need to calculate the value of all services rendered prior to a given date. I am attempting to use a value from the report field.value where field is the name of a control on the report in my filter expression. I've tried

    filter = "test = ' " + field.value + " ' "

    but that doesn't seem to do the trick. What is the format for including a the value of the current field (which is within a group on the report) in a filter expresion?

    Thank you.
    btw, any idea where to find Cal Locklin's (I think) explaination of how to write expressions?

    David A. Volgas, MD

  • #2
    Re: object properties in filter expressions

    Looks ok at first glance. Field is a character type? If not you don't use the same syntax.

    Numeric would be

    filter = "test = " + field.value

    Date would be

    filter = "test = {" + dtoc(field.value) + "} "

    What is test? Why are you trying to use the report object value rather than the field it represents? Where are you trying to use the filter?
    There can be only one.


    • #3
      Re: object properties in filter expressions

      Thank you, Stan.

      My variable is a numeric value, so the second form works fine. I have to re-learn filter expressions every time i try to do something with a variable.

      Again, thank you.
      David A. Volgas, MD


      • #4
        Re: object properties in filter expressions

        Check out the TableSum in the online help files using the search under Index. Tom Cone's explanations are what I think you were referring to---the syntax can be used for all expressions so is quite valuable to learn.
        It is only when we forget all our learning that we begin to know.
        It's not what you look at that matters, it's what you see.
        Henry David Thoreau


        • #5
          Re: object properties in filter expressions

          Write down three simple filters.

          "test = 'abc'"
          "test = 4"
          "test = {01/01/2001}"

          To pass a variable to any of them, all you need to do is put "+ before the variable in the simple filter and +" after it. Then change the fixed value to a character representation of the variable's value.

          First the "+ and +"
          "test = '"+abc+"'"
          "test = "+4+""
          "test = {"+01/01/2001+"}"

          Then the character representation
          "test = '"+"abc"+"'"
          "test = "+"4"+""
          "test = {"+dtoc({01/01/2001})+"}"

          Sometimes you will see

          "test = "+"4"+""


          "test = "+"4"

          because the +"" is meaningless (tacks a blank on the end).

          More commonly you will see

          "test = "+4

          because Alpha performs automatic conversion of numeric types to character when concatenating a numeric to a character value. Ever created an index on two fields, one character and one numeric?
          There can be only one.


          • #6
            Re: object properties in filter expressions

            <<Disclaimer: Comments not directly pertinent to a solution to your question are purely editorial and may be freely ignored. No slight intended.
            Any comment directly concerned with a solution to your thread carries a money back guarantee.
            February 2010 only, double your money back if not completely satisfied.>>

            I 'm holding out for a better offer....Maybe March..a Rebate on the Purchase Price?
            First Love


            • #7
              Re: object properties in filter expressions

              Looks like I may not have finished the example completely.

              The last step is to drop in the variable's name in place of the previously used fixed value.

              Then the character representation
              "test = '"+"abc"+"'"
              "test = "+"4"+""
              "test = {"+dtoc({01/01/2001})+"}"

              Then the variable substitution, where the variable is the appropriate type
              "test = '"+variablename+"'" --------for character
              "test = "+variablename+"" --------for numeric
              "test = {"+dtoc(variablename)+"}"-for date
              There can be only one.


              • #8
                Re: object properties in filter expressions

                Originally posted by Stan Mathews View Post
                Looks like I may not have finished the example completely.

                Any comment directly concerned with a solution to your thread carries a money back guarantee.
                February 2010 only, double your money back if not completely satisfied.
                I want my money back - double.. on Sat - triple????
                Al Buchholz
                Bookwood Systems, LTD
                Weekly QReportBuilder Webinars Thursday 1 pm CST

                Occam's Razor - KISS
                Normalize till it hurts - De-normalize till it works.
                Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                When we triage a problem it is much easier to read sample systems than to read a mind.
                "Make it as simple as possible, but not simpler."
                Albert Einstein



                • #9
                  Re: object properties in filter expressions

                  Just send me a Paypal request for the amount in question.

                  With the appropriate documentation.
                  There can be only one.