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

setting dialog field value on onbeforerecordinsert event handler

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

    setting dialog field value on onbeforerecordinsert event handler

    I am calling the following xbasic function on onbeforerecordinsert event handler to set the dialog component field value.

    dim sql as c
    dim args1 as sql::arguments
    dim LNxtId as c
    args1.set("paramtp","CUSTOMER")
    args1.set("prfx","C")
    sql = "Select dbo.fn_nextsequence(:paramtp,:prfx) " //User defined sql function
    if (cn.execute(sql,args1))= .f. then
    acmastupdate = "alert('" + js_escape(cn.callResult.text) + "');"
    else
    LNxtId = cn.ResultSet.Data(1)
    end if
    e.control.cust_code = LNxtId

    but value is not effected in submit my data.
    I tried to dirty the field by the following command
    e.dirtyColumns.r1 = e.dirtyColumns.r1 + crlf()+"CUST_CODE"+crlf()
    but i get error.

    Please help me to get out of this error.

    #2
    Re: setting dialog field value on onbeforerecordinsert event handler

    I know you have difficulty starting out in alpha five ( read your other post) and I see that no one has answered this one yet and possibly this prompted your other post.
    as I see in this post it looks like you are trying to get the new record id from customer table and want to insert it into the current dialog.
    and you are not getting anywhere with it.
    instead of trying to find an answer how to populate the id of a dialog, may I ask what are you trying to achieve and why you chose this approach?
    if I understand your logic I could try to help.
    below my signature there is link for a blog please take a look, also there are many people in this board, they have posted valuable code and they routinely contribute to the forum. you can take a look at their post and follow the method they implement. if you scan the board you will recognize who contributes generously, they are valuable addition to alpha software.
    thanks for reading

    gandhi

    version 11 3381 - 4096
    mysql backend
    http://www.alphawebprogramming.blogspot.com
    [email protected]
    Skype:[email protected]
    1 914 924 5171

    Comment


      #3
      Re: setting dialog field value on onbeforerecordinsert event handler

      Thanks Gandhi, I can see from other threads you valuable contribution in this forum, i appreciated.
      My application scenario is as follows,
      - I am creating a dialog form to record customer information
      - Customer Table (SQL) contains Cust_Key (Auto ID) Primary Key, Cust_Code unique index key, cust_name, etc...
      - I generate next cust_code value from another table (not Customer table)
      - I want to save this value in cust_code field in Customer table when i submit my customer dialog form.
      - I am trying to assign this value on server side afterdialogvalidate event handler before ExecuteServerSideAction("Save Data::save_datatocustmast").( Am i wrong ?).
      - i tried e.control.<dialogfieldvalue> method and e.arguments method , but i am not able to achieve my requirement.

      Comment


        #4
        Re: setting dialog field value on onbeforerecordinsert event handler

        okay

        this needs to go in the afterValidate event before the record save action, not in the event you picked.
        also I have corrected your code. take a look at this modified code.
        if you want I will post a video later on.

        (ps: this assumes you have dimmed and executed connection and verified the connection took place and your function works correct
        the change below assumes you are getting a number, the one you want)

        Code:
        dim sql as c
         dim args1 as sql::arguments
         dim LNxtId as c
         args1.set("paramtp","CUSTOMER")
         args1.set("prfx","C")
         sql = "Select dbo.fn_nextsequence(:paramtp,:prfx) " //User defined sql function
         if (cn.execute(sql,args1))= .f. then
                 acmastupdate = "alert('" + js_escape(cn.callResult.text) + "');"
                 end function
          else
                   LNxtId = cn.ResultSet.Data(1)
                    e.dataSubmitted.cust_code = LNxtId
                     e.dirtyColumns = e.dirtyColumns + crlf() +"CUST_CODE"
         end if
        edit:
        http://screencast.com/t/bpxwqgGm
        edit2: with alert message
        http://screencast.com/t/Cge2kQIdxby
        Last edited by GGandhi; 05-30-2014, 07:10 AM.
        thanks for reading

        gandhi

        version 11 3381 - 4096
        mysql backend
        http://www.alphawebprogramming.blogspot.com
        [email protected]
        Skype:[email protected]
        1 914 924 5171

        Comment


          #5
          Re: setting dialog field value on onbeforerecordinsert event handler

          Thanks Mr.Gandhi.

          it worked like charm... thanks

          Comment

          Working...
          X