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

SQL arguement in a Where statement

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

    SQL arguement in a Where statement

    In a Grid Component using an AlphaDAO, I am having problems using an arguement in the filter for the Query SQL Select.

    Example:
    SELECT FACILITY.NAME, FACILITY.USERTYPES FROM FACILITY FACILITY WHERE USERTYPES LIKE '%:argType%'

    argType is defined as a character populated by the variable session.sType
    :argType = "1"

    The above statement does not work for me. When I hardcode the "1" ( USERTYPES LIKE '%1%' ) the Grid Select works.

    Using an override setting on the A5w page works successfully when I concat the session variable in place of the arguement:

    CS.SQL = "SELECT FACILITY.NAME, FACILITY.USERTYPES FROM FACILITY WHERE USERTYPES LIKE '%"+alltrim(session.sType)+"%'"

    Additional info,
    I've also tried to trim argType without success:
    SELECT FACILITY.NAME, FACILITY.USERTYPES FROM FACILITY FACILITY WHERE USERTYPES LIKE '%alltrim(:argType)%'

    #2
    Re: SQL arguement in a Where statement

    Why are you hand-coding the SQL in a grid?

    Or in which context are you using a filter? (See screenshots)
    Last edited by NoeticCC; 07-08-2009, 03:19 PM.

    Comment


      #3
      Re: SQL arguement in a Where statement

      I tried using the component prompts for Table/View, but it did not work (img1.png).

      Then I tried the SQL Select Statment prompts (img2.png). Again it did not work

      The argument is declared with the Define Arguments builder (img3.png)

      Did this answer your question? Or did I miss the mark?
      Last edited by roberto; 07-08-2009, 04:20 PM.

      Comment


        #4
        Re: SQL arguement in a Where statement

        Originally posted by roberto View Post
        I tried using the component prompts for Table/View, but it did not work (img1.png).

        Then I tried the SQL Select Statment prompts (img2.png). Again it did not work

        The argument is declared with the Define Arguments builder (img3.png)

        Did this answer your question? Or did I miss the mark?
        I'd think it was simply

        USERTYPES = :argType

        Comment


          #5
          Re: SQL arguement in a Where statement

          Unfortunately a straight 'equal to' can not be used.

          USERTYPES is actually a comma-delimited string of 3-digit numbers. USERTYPES could have values like "002,345,876" or "993,001,656,344,002" or etc

          Therefore I tried using the LIKE statement. The LIKE works as an override in the A5W page. Unfortunately, I am not able to get it to work in the standard component prompts.

          Comment


            #6
            Re: SQL arguement in a Where statement

            Originally posted by roberto View Post
            Unfortunately a straight 'equal to' can not be used.

            USERTYPES is actually a comma-delimited string of 3-digit numbers. USERTYPES could have values like "002,345,876" or "993,001,656,344,002" or etc

            Therefore I tried using the LIKE statement. The LIKE works as an override in the A5W page. Unfortunately, I am not able to get it to work in the standard component prompts.
            Aah... Hm, I will have a play but I would have tried something like:

            ".. WHERE :arg IN (USERTYPES)" but not 100% sure it works that way around.

            Comment


              #7
              Re: SQL arguement in a Where statement

              In mySQL this works:

              SELECT ID, UserTypes
              FROM in_test
              WHERE UserTypes LIKE concatenate('%', :arg1, '%')

              Comment


                #8
                Re: SQL arguement in a Where statement

                That works beautifully with SQL Express 2005 also.

                Thank You!

                Comment


                  #9
                  Re: SQL arguement in a Where statement

                  Originally posted by roberto View Post
                  That works beautifully with SQL Express 2005 also.

                  Thank You!
                  Good to know, as the concatenate syntax was new to me before I worked with mySQL

                  Comment

                  Working...
                  X