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

Concatenating arguments in an SQL filter

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

    Concatenating arguments in an SQL filter

    I'm defining an SQL filter in the Report Print Genie on a tabbed UI builder, and wondering if it's possible to concatenate arguments that are entered by the user at run-time.

    My current filter is as follows:
    AUTH = 1 AND COMB = :whatUser+ '' + :whatMonth+ '' + :whatYear

    where whatUser, whatMonth, and whatYear are character arguments that are defined via prompt at run-time.

    Records have a combined field (COMB) that is comprised of these 3 details; name, month and date.
    By filtering the COMB field I planned to display records from within that COMB group.

    Using the filter above, trying to print a report returns an error.
    Does the SQL Builder allow for concatenated arguments? I'm assuming my syntax is bad but I don't know either way.

    #2
    Re: Concatenating arguments in an SQL filter

    I don't really understand what you're trying to do, but there is a concatenate("fee", "foo", "fum") to get feefoofum

    Comment


      #3
      Re: Concatenating arguments in an SQL filter

      The field that I need to filter on stores a combination of the username, month and year e.g. "john doeMarch2010". The report can take them in individually as arguments, but I need to concatenate them into one string to use with the filter.

      expenses_report.jpg

      I've been trying to do the concatenation as a part of the sql filter definition:

      AUTH = 1 AND COMB = (:whatUser + :whatMonth + :whatYear)

      The report is displaying records now, but it seems to be ignoring the filter expression.
      Last edited by RaEd.; 01-10-2012, 06:26 AM.

      Comment


        #4
        Re: Concatenating arguments in an SQL filter

        Uh oh! It was only working at all because I'd made a typo in the filter argument
        I'm back to displaying an error when printing the report

        Report did not print. Error reported was:

        Layout name: Expenses@C:\A5Webroot\jmtest2.alb
        Layout type: report

        SQLReporting 9 - Could not create ResultSet from DataSource definition. Could not execute query against Database. Error reported was: Success


        It just doesn't like that expression.

        Comment


          #5
          Re: Concatenating arguments in an SQL filter

          As usual it was all perfectly simple!
          The combination of my typo and the value passed by one of my static defined arguments was messing it up.

          So, to clarify, you can perform concatenation on arguments in report filters!
          Since this thread is about nothing but my typos, I'll delete it (if I can) to get it out of the way xD

          Comment


            #6
            Re: Concatenating arguments in an SQL filter

            I just came across a problem that I was having that I accidentally resolved, although I repeated it and took notice the second time.

            If you make any changes to the argument definitions in the report genie you need to set the argument values again or they won't take the new settings.

            The problem I had was that I had changed a numeric type argument to a character type argument, saved and published and expected to work. This was returning an error upon printing the report because the SQL filter definition was still trying to concatenate a character type with a numeric type. To fix it I simply selected each of my argument names in the report genie, clicked on the Set Argument Value button, inserted the field placeholder again and then clicked OK.

            I could see that the changes had been made in the Report Definition > Argument bindings property in the Tabbed UI Controls section of the builder.

            Comment

            Working...
            X