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

"Invalid report filter express"

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

    "Invalid report filter express"

    I have a filter that works properly in an Xbasic query - the script then opens a browse, and the correct records are shown.

    I then tried creating a new report, based on the same table, and selected "Base report on currently selected records". That's when I get the error.

    I also tried copying the filter to the report's filter. It evaluates properly in the expression builder, but I get the same error when trying to run a report.

    Here's the filter (the variables are global):

    ("amada"$desc .or. "amada"$partno .or. "wikus"$desc .or. "wikus"$partno .or. "prochem"$desc.or. "prochem"$partno) .and. ship_date "= var-"d1 .and. ship_date "= var-" d2

    #2
    RE:

    Bill:
    ""I also tried copying the filter to the report's filter. It evaluates properly in the expression builder, but I get the same error when trying to run a report. ""
    Make sure you check base report on additional filter: none.
    You did not specify the error: I am guessing: no pages in this report
    Gabe

    Comment


      #3
      RE:

      The error I get is, "Invalid report filter expression".

      Yes, I did check None when I put the filter in the report.

      Comment


        #4
        RE:

        Bill:
        next step would be to double check the field(s) references: they might not be adequate(for instance if report is based on a set where you have to specify the table/field etc.)
        Gabe

        Comment


          #5
          RE:

          Did you cut and paste the expression

          ("amada"$desc .or. "amada"$partno .or. "wikus"$desc .or. "wikus"$partno .or. "prochem"$desc.or. "prochem"$partno) .and. ship_date "= var-"d1 .and. ship_date "= var-" d2

          because there is an unacceptable space in var-" d2 should be

          var-"d2.
          There can be only one.

          Comment


            #6
            RE:

            Stan, you're a genius! That was the problem. Thanks.

            This is one of those cases where I missed something obvious, and why this board is such a valuable resource.

            Comment


              #7
              RE:

              Just cut and pasted your expression into the interactive editor. Looked for mis-matched quotes, etc that would be shown by the expression/syntax colorizer. The problem section just didn't look right.
              There can be only one.

              Comment


                #8
                RE:

                ""It evaluates properly in the expression builder""
                How?
                Gabe

                Comment


                  #9
                  RE:

                  When you open the expression builder (for example, when creating a filter in a report), the message at the bottom will either say ""invalid or incomplete expression"", or it will evaluate to a result. In the case of my expression, it evaluated to False, telling me that it was a valid expression ("False" meant that the current record did not meet the filter criteria). In other cases, a valid expression will evaluate to a number or character value. In each of these cases, showing something other than ""invalid or incomplete expression"" usually means that the expression is correct.

                  Comment


                    #10
                    RE:

                    Ok.
                    When I read your statment inititally, I took it to mean that the elements of the expression were correct since it evaluated and since a logical expression will show as "L" without necessarily showing true or false.
                    Gabe

                    Comment

                    Working...
                    X