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

BeforeValidateNewRecords

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

    BeforeValidateNewRecords

    Hi,

    I used the BeforeValidateNewRecords function in the Event sewction of a grid to give a field a value (see below).
    This works fine, but I get it working only for a field that is visible and not a label. I would like to do this for a hidden field, or at least a label.

    Is this possible?

    GReetings, Ren�

    function BeforeValidateNewRecords as v (DataSubmitted as P, Args as p, PageVariables as p)
    with PageVariables
    DataSubmitted.User_Id = session.__protected__PraktijkUserID
    end with


    end function
    Ren�
    Windows 7, V11

    #2
    RE: BeforeValidateNewRecords

    Notice that session is not passed directly into the function, so you cannot use session."whatever" directly. Instead use PageVariables.session."whatever"

    Lenny Forziati
    Vice President, Internet Products and Technical Services
    Alpha Software Corporation

    Comment


      #3
      RE: BeforeValidateNewRecords

      Lenny,

      the variabel was passed to the field, but only when the field was not a label and was visible.

      I changed the function according to your instructions, but the behaviour stays the same.

      What I encounter is this:
      a - when I insert a record, I can only change the value of a visible field that is not a label. (I do this in the BeforeValidatNewRecord event).
      b - when I only edit records (without inserting one) the system inserts a record because it changed the field of the insert-row.

      So, here's two questions:

      1- What should I do if I want to add a value to a hidden field when I insert a record?

      2- How do I prevent that, if I edit a record, the system inserts a record because it fills a field in the blank row?

      Greetings, Ren�
      Ren�
      Windows 7, V11

      Comment


        #4
        RE: BeforeValidateNewRecords

        alpha five adds a new row if the new row is 'dirty'

        by 'dirty' we mean that one or more controls in the new row have a different value than their original value (when the page was displayed).

        if you set the value of the hidden control in the new row, (when all of the other controls on the row have not been edited by the user before he hit 'submit' -- then a5 will see this as a 'dirty' row and will add a new record to the database).

        so, in your 'beforevalidateNEWrecord()' event, you have to do more work. you have to check all of the submitted values and only if you detect that the user has actually entered a value into one of the visible fields should you set the value of the hidden field.


        on the issue of 'labels'. i am not sure if i understand your question, but it seems like you are trying to manipulate the value that is shown in a label control in the event. you can't do this. the event only deals with data that is submitted to the server when the user clicks the 'submit' button. 'label' controls don't submit data to the server.

        Comment


          #5
          RE: BeforeValidateNewRecords

          alpha five adds a new row if the new row is 'dirty'

          by 'dirty' we mean that one or more controls in the new row have a different value than their original value (when the page was displayed).

          if you set the value of the hidden control in the new row, (when all of the other controls on the row have not been edited by the user before he hit 'submit' -- then a5 will see this as a 'dirty' row and will add a new record to the database).

          so, in your 'beforevalidateNEWrecord()' event, you have to do more work. you have to check all of the submitted values and only if you detect that the user has actually entered a value into one of the visible fields should you set the value of the hidden field.


          on the issue of 'labels'. i am not sure if i understand your question, but it seems like you are trying to manipulate the value that is shown in a label control in the event. you can't do this. the event only deals with data that is submitted to the server when the user clicks the 'submit' button. 'label' controls don't submit data to the server.

          Comment


            #6
            RE: BeforeValidateNewRecords

            ok, thanks.

            So my logic was out of line.
            What I want to accomplish is this:

            When a users inserts a record, I want to be fill a field with a session value. That field should not be visible to the user.

            I understand from you that I should make something like this:

            if
            fieldOne=""
            fieldTwo=""
            fieldThree= ctod("")
            etc.
            then
            hiddenField=sessionvar
            end if

            Right?

            Ren�
            Ren�
            Windows 7, V11

            Comment


              #7
              RE: BeforeValidateNewRecords

              ok, disregard this. I found the right way to do it in the help files.
              Ren�
              Windows 7, V11

              Comment

              Working...
              X