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

Using Wildcard w/Variables

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

    Using Wildcard w/Variables

    Is there a way to use the wildcard "*" when using the �Variable Ask User� function in a report. I have a number of reports that run based on the contents of either one or multiple fields. Since users sometime don't enter data uniquely (can you imagine) it would be nice to be able to use the Wildcard to find all of the data that I�m looking for. Any suggestions would be appreciated.

    Thanks

    Bob

    #2
    RE: Using Wildcard w/Variables

    Robert,

    Check out the SMATCH functions. You might be able to do what you want using these functions with "OR"'s rather than "AND"'s in the report detail filter. There are two SMATCH functions, one for character fields and one for memos. I think the functions return a true if all of one string is found in another string or field value.

    Comment


      #3
      RE: Using Wildcard w/Variables

      Hi Robert,

      >>Is there a way to use the wildcard "*" when using the �Variable Ask User� function in a report

      Comment


        #4
        RE: Using Wildcard w/Variables

        I would agree with John Zaleski's approach - get some information from the variable, then use that in a filter in the report. There is also a very slick function you can use that is similar to SMATCH but I find to be easier. Here's an example:

        In the ask variable, set the value to a global variable. Let's say the value is "ABC". Now, in the report filter, use this function:

        "ABC"$FIELD_NAME

        This means that the program will find the string ABC in the field FIELD_NAME. (This is the same as the A4 function *ANY).

        You have to be a little careful, since it will find the string ANYWHERE in the field.

        Another approach would be to use:

        *FIRST(FIELD_NAME,"ABC"), which will find the string ONLY if it is at the beginning of the field. One tip about this method - if you wanted to find the name ABC but NOT ABCDE, have the user put ABC plus a space in the prompt box. this will prevent the filter from finding ABCDE.

        Comment


          #5
          RE: Using Wildcard w/Variables

          Thanks to All:

          Let's see if I got the picture here. I can set the ask_user variable within the report as a calculated field, then set the records filter using this calculated variable field with the *ANY or SMATCH functions. I'll try that today and see what happens and let you know.

          Does anyone know why we can use the wildcard in the query by form, which in my mind is similar, and not in the ask_user function. They seem to be the same to me.

          Anyway, thanks for all the input.

          Bob

          Comment


            #6
            RE: Using Wildcard w/Variables

            Bill:

            The *ANY function works fine. I created a calculate field that asks for a character input. That looks like:

            "What_Item" = VAR->ASKC_What_Item_

            Then in the Report Details - Filter I set the following condition:

            *ANY(Field_Name,Calc->What_Item).AND.--- (any other conditions you need)

            It works fine. It will find all records that have any string of data that you enter in the variable field. It does appear to be case sensitive however for characters.

            Thanks for your help. This is a great find.

            Best:

            Bob Fishell

            Comment


              #7
              RE: Using Wildcard w/Variables

              I use wildcards with ASK variables in many of my reports and forms. Altho I don't use the genie, but write the expression. Lets say I only want a report of customers that start with "MA" since the first of the year.

              dtoc(date)>"01/01/00".and.smatch((customer),Var->Askc_Name_+"*")

              If you want any occurance of the variable you would add another "*"+ before the variable, and only occurances that end with the variable, remove the trailing +"*"

              Comment


                #8
                RE: Using Wildcard w/Variables

                Mick:

                Thanks. Never thought of that approach. I'll try that one also.

                I have noticed that this type of variable search can't find those fields which are blank. I needed to run a seperate report to handle those occasion. Otherwise it's working great.

                Thanks to all for the input.

                Bob

                Comment

                Working...
                X