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

onBeforeSQLCommandExecute in Grid, Getting Data from Controls

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

  • onBeforeSQLCommandExecute in Grid, Getting Data from Controls

    I'm sure that this is a really basic question to those who know, but I can't find an answer anywhere. I'm trying to use the onBeforeSQLCommandExecute server side event in order to customize how the SQL is written to my database. However, I can't figure out how to fill my arguments with the data from the grid fields.

    I tried args.set("arg1", e.datasubmitted.<fieldname>) and args.set("arg1", e.data.<fieldname>), as well as a number of other permutations, with no luck. Would appreciate if someone would point me in the right direction. Thanks.

  • #2
    Re: onBeforeSQLCommandExecute in Grid, Getting Data from Controls

    first you need to dim the args as in

    Dim args as sql::arguments

    Then you use args.add("arg1",e.dataSubmitted.myfiledname), don't forget that the data is always character, therefore if your arg needs to be some other data type, use convert_type() to change it.

    Comment


    • #3
      Re: onBeforeSQLCommandExecute in Grid, Getting Data from Controls

      Still not working. I get the following error when I submit:

      An error occurred in the onBeforeSQLCommandExecute event handler. Error reported: command: args.add("WGID", e.datasubmitted.workgroupid) Property not found
      e.datasubmitted subelement not found.
      Here's the code:

      Code:
      dim cn as sql::Connection
      dim args as sql::Arguments
      dim sqlcall as c
      dim flag as l
      
      e.cn.PortableSQLEnabled = .f.
      e.SQLCommandWasHandled = .t.
      
      args.Clear()
      args.add("WGID", e.datasubmitted.workgroupid)
      args.add("EmpID", e.datasubmitted.employeeid)
      args.add("CrBy", e.datasubmitted.createdby)
      Is there something besides e.datasubmitted, like an e.data-to-be-submitted, since it hasn't actually be submitted yet?

      Comment


      • #4
        Re: onBeforeSQLCommandExecute in Grid, Getting Data from Controls

        Yes sorry those events handle the data that is submitted a whole different way! Go to the videos here and search for SQLCommandExecute, this will bring you to video 78 or SSE12 which has 6 video's all about these events

        Comment


        • #5
          Re: onBeforeSQLCommandExecute in Grid, Getting Data from Controls

          Lance,

          I watched those videos last night and did not see where they address the topic of arguments. The example used in the videos does not utilize arguments at all. I'm still completely at a loss here. This functionality does not seem to be documented anywhere.

          Comment


          • #6
            Re: onBeforeSQLCommandExecute in Grid, Getting Data from Controls

            Originally posted by 10001 View Post
            The example used in the videos does not utilize arguments at all. I'm still completely at a loss here. This functionality does not seem to be documented anywhere.
            The documentation is mostly in the function prototype. Argument handling is explained as so:
            Code:
            'e.argsXML = The XML for the SQL::Arguments object with value for the arguments used in the statement
            'e.argsXML contains the argument values for the data that was submitted when the user clicked the submit button. 
            'e.argsXML contains the new and old values for all fields on the Grid.
            'Note: To convert e.argsXML into a sql::arguments object you would do:
            '		dim myargs as sql::arguments
            '		myargs.xml = e.argXML
            
            'If your Grid sets arguments for the initial Query, these argument values are stored in XML format in:
            'e.rtc.ArgumentsQuery.XML
            So, in your example you would use:
            Code:
            dim cn as sql::Connection
            dim args as sql::Arguments
            
            args.xml = e.argXML
            
            dim sqlcall as c
            dim flag as l
            
            e.cn.PortableSQLEnabled = .f.
            e.SQLCommandWasHandled = .t.
            However, the grid doesn't have e.datasubmitted available so you now you have to find the values you want to set your arguments to. These are in e.rv.V.Rwhaterver the current row number is. You have some more work to do to harvest the values to put into your arguments. Everything you need is availiable. Finding it and figuring out how to get it is where the fun starts.

            Also, unless you need a new connection you can just use the e.cn sql connection object that already exists and not bother with "dim cn as sql::Connection".
            Jim Coltz
            Alpha Custom Database Solutions, LLC
            A5CustomSolutions.com
            [email protected]

            Comment


            • #7
              Re: onBeforeSQLCommandExecute in Grid, Getting Data from Controls

              I don't believe the "e.DataSubmitted" structure is used in this particular event. I use "request.variables.V.R(row_number).(field_name)". Enter "request.variables.V" in the watch variables section of the debugger and expand the row number variable. You should see your field variables. The row number is stored in "e.rowNumber".

              Edit: Jim's post beat mine. You can use either "request.variables.V" or "e.rv.V". The row data is stored in both constructs, but the documentation in the comments section says we should start using "request.variables".
              Last edited by DaveF; 04-01-2013, 01:18 PM.

              Comment


              • #8
                Re: onBeforeSQLCommandExecute in Grid, Getting Data from Controls

                Yes, we should be using the request object instead of e.rv.V. (old habit)
                Jim Coltz
                Alpha Custom Database Solutions, LLC
                A5CustomSolutions.com
                [email protected]

                Comment


                • #9
                  Re: onBeforeSQLCommandExecute in Grid, Getting Data from Controls

                  Thanks for the help. By the way, e.argXML did not work for me, it's apparently e.argsXML. Working code below:

                  Code:
                  dim cn as sql::Connection = e.cn
                  dim args as sql::Arguments
                  
                  args.xml = e.argsXML
                  
                  dim sqlcall as c
                  dim flag as l
                  
                  e.cn.PortableSQLEnabled = .f.
                  e.SQLCommandWasHandled = .t.
                  
                  args.add("WGID", request.variables.V.R_1.workgroupid)
                  args.add("EmpID", request.variables.V.R_1.employeeid)
                  args.add("CrBy", request.variables.V.R_1.createdby)

                  Comment

                  Working...
                  X