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

Required value validation unreliable?

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

    Required value validation unreliable?

    I would like to know if anyone else is experiencing unreliability as I am with the 'Required Value' under Validation in a detailed view grid. The required value feature is usually set as shown in the screen shot below:
    validation2.png

    However many times this simply does not work and some validation using Xbasic code has to be set in the 'CanInsertRecord' server side event. Does anyone else experience this?

    #2
    Re: Required value validation unreliable?

    I don't know if I have seen this on a Detail view of Grid, but this problem happens to me on a UX and I have to put server-side code to duplicate my client-side validation; very annoying. I don't know if the "Blank is Null" options helps this issue or not.

    Comment


      #3
      Re: Required value validation unreliable?

      Originally posted by RichCPT View Post
      I have to put server-side code to duplicate my client-side validation
      If you really want to validate something you always have to have server side validation.

      Comment


        #4
        Re: Required value validation unreliable?

        Originally posted by kkfin View Post
        If you really want to validate something you always have to have server side validation.
        I don't think so. Not for required data... or validating against other client-side data. Why make a callback when you don't need to.

        In the Detail View properties... Field validation setting... is this set to All Fields? If you want to check for required data, this should be set to All Fields. You may not tab or click into the control you're checking. If you don't get into that control, and Field validation setting is set to dirty fields only, then that field will not be validated.

        If you don't want to do this, then use the Client-side Event, canDetailViewSubmit. Put code in here to validate whatever you want (as long as the data you want to work with exists at the client side). If whatever you're checking is invalid, then return false. This stops the submit.

        Comment


          #5
          Re: Required value validation unreliable?

          Originally posted by Davidk View Post
          I don't think so. Not for required data... or validating against other client-side data. Why make a callback when you don't need to.

          In the Detail View properties... Field validation setting... is this set to All Fields? If you want to check for required data, this should be set to All Fields. You may not tab or click into the control you're checking. If you don't get into that control, and Field validation setting is set to dirty fields only, then that field will not be validated.

          If you don't want to do this, then use the Client-side Event, canDetailViewSubmit. Put code in here to validate whatever you want (as long as the data you want to work with exists at the client side). If whatever you're checking is invalid, then return false. This stops the submit.
          When client side validated data submit happens client side code has not anymore access to submitted data.

          But so called malicious user and testing developer has access to data and header information and so they can still corrupt the data just before it is really submitted to the server. This is also true with hidden :) fields.

          This is the reason why you need to always do server side validation.
          Client side validation is just for better user experience. The real validation is done in server.

          It is developers choice to validate in server or not but it is dangerous to give to other developers impression to relay on client side validation. The problem is that somebody may belive you.

          Comment


            #6
            Re: Required value validation unreliable?

            I don't think that's where the problem is.

            Comment

            Working...
            X