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



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

Arguments in Stored Procedure

  • Filter
  • Time
  • Show
Clear All
new posts

  • Arguments in Stored Procedure

    Need some help from someone who knows how V11 handles insertion of arguments. I'm using mysql, and a grid. Before I execute the grid, I execute a stored procedure to GROUP_CONCAT some results so that I can put them in a session variable, then use them in an IN clause. Simplified example:

    SELECT * FROM tasks WHERE EmployeeID IN (5,9,14,34)
    My problem is when I try to use the session variable with an argument in the SQL query. It's set up like this:

    SELECT * FROM tasks WHERE EmployeeID IN (:argument1)
    The problem appears to be that, since the session variable and the argument are character type variables, Alpha's automatically putting quotes around the argument when it inserts it into the SQL statement. However, I don't want that, because that causes the query to process incorrectly.

    Is there any way to avoid this? I tried modifying the code in the onSQLSelectQuery event, but it didn't work very well with my search part. It would work fine the first time, then error out on any subsequent search ("Error expanding grid part template: Variable 'Data' not found.")

    I came up with a workaround that in theory should work, but isn't. If Alpha is adding quotes, I could actually add another set of quotes and some commas and get it to work correctly:

    SELECT * FROM tasks WHERE EmployeeID IN ("",5,9,14,34,"")
    Unfortunately, this didn't work either, regardless of the method I tried (escaped double quotes, single quotes, the QUOTE function...)

    Anybody have any ideas on this?



  • #2
    Re: Arguments in Stored Procedure

    I don't know if this helps

    This is from version 12 check to see if Alpha supports the IN Clause in V11 I guess it will. If this helps there is a video

    UX and Grid Component - Action Javascript - Print Report Action - SQL Reports - IN Clause - When using Action Javascript to display a report based on a SQL datasource, you might want to use the SQL IN clause in your report filter.

    Watch Video
    Download Component (Requires a connection string called 'Northwind' to sample Northwind database)

    For example, you might have a checkbox control and you want to print the report showing all values checked in the checkbox control. The syntax for the IN clause is as follows:
    SELECT * from PRODUCTS WHERE COLOR IN ('red', 'green', 'blue')
    Translating this to use arguments:
    SELECT * from PRODUCTS WHERE COLOR IN (:whatcolor)
    In the above example, you cannot use a simple character argument. You must use a special 'array argument'.
    In the Action Javascript builder, when you define arguments to use in the report filter, a special naming convention is used to indicate that the argument is an array argument. If the argument name starts with 'array_', the argument is assumed to be an 'array argument'

    TIP: Here is some sample code that shows how you use Xbasic to populate an 'array argument':
    dim args as sql::arguments
    dim tempArray[0] as c
    tempArray[] = "red"
    tempArray[] = "blue"
    tempArray[] = "green"