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

Filtering records for reports

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

    Filtering records for reports

    I have a character field in a table that I would like to use to filter records to print in a report. The table is an equipment list from sinks to fans and ?. I am trying to print only the items which have an electrical value that is posted in the "voltage" field. The report detail section for records allows you to filter records but I have not figured out the expression to use for this character field. The voltage field consists of values such as 208/3/60 or 120/1/60. I have chosen to use a character field as this allows me to have a simple mask in the field rules.

    Any examples would be appreciated.

    Larry

    #2
    RE: Filtering records for reports

    Larry:

    Try

    .not.isblank("fieldname")
    I'll bet that will get it.

    Ken

    Comment


      #3
      RE: Filtering records for reports

      Larry:

      I answered too quickly

      .not.isblank("Voltage")

      Sorry

      Ken

      Comment


        #4
        RE: Filtering records for reports

        Hi Ken
        I tried using the isnotblank(field) expression but I end up with an error. If I evaluate the expression before saving it comes up with "no such value" and when I do a print preview it comes up with "error occured parsing filter expression-no such field".

        I tried creating a new report, using different fields, different tables and it always comes back with the same errors.

        Any ideas of what could be wrong?

        Larry

        Comment


          #5
          RE: Filtering records for reports

          Larry:

          I'm an old A4 guy who doeesn't know the difference from isnotblank() and .not.isblank() so...... I use the latter. I just tested it with my own table/form and it works with this syntax.

          .not.isblank("voltage")

          Are you putting the field name in quotes? This syntax checks in the expression builder without errors and performs as advertised on the sort.

          Try again and let me know

          Ken

          Comment


            #6
            RE: Filtering records for reports

            Ken
            I tried it a few more times (isnotblank), both with and without the quotations and it finally took with the quotations. I still am not sure what I was doing wrong. I did notice that there is a different menu selection in the filter expression builder. If you start with nothing in the expression box, the selection of expressions is less than if you already have an expression in the expression box and go to edit it.
            Also, if you use the expressions directly from the menu (double clicking), it does not put the quotations around the field value.???

            Anyway, thanks very much for the assistance and this has solved one of my issues.

            Larry

            Comment


              #7
              RE: Filtering records for reports

              Is voltage a numeric field (it probably shouldn't be). If so you will run in to anomalies using isblank syntax.

              You could add a logical field, "electrical". Another way would be to make sure "voltage" is defined as a character field and place the entry "na" in the records for non-electrical equipment. Then you could easily filter on "Voltage='na'".

              Bill
              Bill Hanigsberg

              Comment


                #8
                RE: Filtering records for reports

                Hi Bill

                The isblank, isnotblank seems to work quite well for the character field. What sort of issues do you see if I use these in a numeric field?

                The "voltage" field is a character field and your suggestion sounds like a good idea. I wonder why some of these simple things don't jump out at me when I'm stuck.

                Thanks for the info.

                Larry

                Comment


                  #9
                  RE: Filtering records for reports

                  " What sort of issues do you see if I use these in a numeric field?"

                  Unpredictably there might be a zero rather than the field being really blank. If the field had to be numeric you could insert a negative value (e.g. -100) and filter on that.

                  In this case character is more appropriate. You will never be doing arithmatic on the voltage ratings of different products.

                  Bill
                  Bill Hanigsberg

                  Comment

                  Working...
                  X