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

Filter syntax

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

    Filter syntax

    I have a report in which I need to only show records that are outside of a user entered range.
    For example: if the user enters 5, then for the field in question, any number greater than 5 or less than negative 5, that record will show on the report.
    If the field value was 4, then that record will not appear in the report and so on.

    Here is what I've been trying. I think it's close but I'm missing something.
    (-Sku_Master->Sm_Percent_Variance<=(Sku_Master->Sm_Percent_Variance=VAR->ASKN_Minimum_Percentage_Variance:__)<=Sku_Master->Sm_Percent_Variance)

    Thank for any help.

    #2
    Re: Filter syntax

    You're complicating things with the ask variable. A form variable would allow you to write something like

    between(Sku_Master->Sm_Percent_Variance,some_variable*-1,somevariable)

    Almost any way you write it with an ask variable is going to request the ask variable twice.
    There can be only one.

    Comment


      #3
      Re: Filter syntax

      Stan, that was my backup plan. I'll just tell my customers that it's a feature instead of my lack of programming skills

      Thanks for your help.

      Comment


        #4
        Re: Filter syntax

        You could create a little xdialog with action scripting to obtain the variable and use it as above. Just scope it properly.
        There can be only one.

        Comment


          #5
          Re: Filter syntax

          That's a good idea. I went with the between(). Overall, I think it will give them more flexibility that my one-size-fits-all solution that I was going to do.
          I added a message box before the report preview to tell them how to use it properly....now, if only I could get them to read the instructions...

          Thanks.

          Comment


            #6
            Re: Filter syntax

            'Read the instructions'? What does that mean? I Have a couple of users who apparently don't know!
            Robin

            Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

            Comment


              #7
              Re: Filter syntax

              John, some of my apps have a Video Clip for Help in some complex situations.
              And not so complex. Done using Jing and held locally.
              See our Hybrid Option here;
              https://hybridapps.example-software.com/


              Apologies to anyone I haven't managed to upset yet.
              You are held in a queue and I will get to you soon.

              Comment


                #8
                Re: Filter syntax

                @ Robin
                I have sent an email a few times that said to all stupid questions:
                Read the screen
                Read the screen
                Read the screen
                Dave Mason
                [email protected]
                Skype is dave.mason46

                Comment


                  #9
                  Re: Filter syntax

                  Nope. Instructions are only for when things don't work.
                  Like the sign on the petrol (gas) pump. "If all else fails, read the instructions, follow them while trying again"
                  See our Hybrid Option here;
                  https://hybridapps.example-software.com/


                  Apologies to anyone I haven't managed to upset yet.
                  You are held in a queue and I will get to you soon.

                  Comment


                    #10
                    Re: Filter syntax

                    I used to have an app that included a manual and videos on each subject of the app. I was amazed by how many people would flat out refuse to watch the videos.
                    All they had to do was click a button and sit a watch, they didn't even have to install a player.
                    They would rather spend hours of my limited time having me walk them through every process.

                    I recently had a customer complaining that nothing in my app worked at all. After much effort on my part, I discovered the problem.
                    He was pushing the pictures of the buttons of a form in the printed manual rather than on the PC itself.

                    Comment


                      #11
                      Re: Filter syntax

                      My dad used to say "Never underestimate the power of stupidity"
                      See our Hybrid Option here;
                      https://hybridapps.example-software.com/


                      Apologies to anyone I haven't managed to upset yet.
                      You are held in a queue and I will get to you soon.

                      Comment


                        #12
                        Re: Filter syntax

                        John

                        The fastest and easiest way to solve the problem is to charge.

                        Bosses tend to sort the problem out internally if they have been charged for Help documentation and their users aren't folloiwng it.
                        Database Software Solutions Limited
                        www.dbasesolution.co.uk
                        http://www.precise360.co.uk
                        PRECISE360 -
                        LYNCHPIN -

                        Comment

                        Working...
                        X