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

How to set focus to error field when using Validation rules?

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

    How to set focus to error field when using Validation rules?

    I am using Validation rules to validate several fields on a dialog (form). When a user clicks the dialog's Submit button, the cursor does not move to an invalild field. As a result, the user does not know that at least one field is invalid and that the dialog has not been submitted.

    If I write Validation Javascript, I can use the focus() method to move the cursor to an invalid field when the user clicks the Submit button.
    1. Is there a way to move the cursor to an invalid field when using Validation rules?
    2. If not, is there a way to pop up a message box to tell him that there is an invalid field somewhere on the form and that he should scroll the form to find it?

    #2
    Re: How to set focus to error field when using Validation rules?

    Long answer for everything:
    Yes. In the afterValidate client-side event. You can either do a "focus" or "scrollTop" operation to the first object that has the error class. I recommend the scrollTo method. This will guarantee that you will scroll to errors that are not textboxes --- such as radio buttons or check boxes. Without knowing your error class name, though, this is the best I can do:

    Code:
    if(e.hasErrors) {
      //scroll the window to the first element in the DOM that has a class name ending with "EditError"
      jQuery(window).scrollTop(jQuery('[class$="EditError"]:first').position().top);
    }
    If your error class doesn't end with "EditError", this will not work. You will need to figure out what class is added to the field when validation fails for that field and change the text inside the quotes to match. For example, if your error class is called "TestEditError", the code inside the if becomes:

    Code:
    jQuery(window).scrollTop(jQuery('.[B]TestEditError[/B]:first').position().top);
    You could also throw up a message box inside the if(e.hasErrros) {} block that navigates to the error:
    Code:
    var title = 'The title of your popup message box';
    var html = 'The HTML of your popup message box; I suggest you use single quotes around this text --- in case you set <span style="font-weight:bold">attributes</span> for any HTML tags';
    var buttonOptions = 'o'; // the OK button 
    
    // Shiny function called when message box is closed that will scroll to the first error
    var onCloseFunc = function() {jQuery(window).scrollTop(jQuery('[class$="EditError"]:first').position().top);}; 
    
    A5.msgBox.show(title,html,buttonOptions,onCloseFunc);
    If you don't like how the scroll comes out, add some value (like 10) to the position().top to scroll further down the document and subtract from position().top to scroll up.

    Answer to Q1:
    If all of your fields with validation are textboxes, you could call focus on the first one with an error. The only drawback I found to doing this is that it is incredibly difficult to tell that the textbox has focus depending on the styling of your error highlighting:

    Code:
    //in the afterValidate client side event for a dialog:
    if(e.hasErrors) {
      //give focus to the first element in the DOM that has a class name ending with "EditError"
      jQuery('[class$="EditError"]:first').focus();
    }
    Lastly, if you are interested in scrolling all the way to the top of the window, read this thread:

    http://msgboard.alphasoftware.com/al...t=error+scroll
    Alpha Anywhere latest pre-release

    Comment


      #3
      Re: How to set focus to error field when using Validation rules?

      I believe my post in this thread http://msgboard.alphasoftware.com/al...ation-Errors!! covers what your asking.
      Jim Coltz
      Alpha Custom Database Solutions, LLC
      A5CustomSolutions.com
      [email protected]

      Comment

      Working...
      X