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

Help with Validation of Masked Field

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

    Help with Validation of Masked Field

    I have a police report application that requires some unique validation upon starting a new report.

    One field is called "Case Number," and consists of 11 digits in this format: Year, Julian Date, No. of Incidents for the day.

    A typical case number for today would be 13-327-0050, and I have the field masked so that the user is forced to enter the data in the format of XX-XXX-XXXX.

    Another field is called "Date Reported," and is a normal date field. (MM/DD/YYYY)

    In this system the Middle Three digits of the Case Number (Julian Date) must always match the Julian Date for the Date Reported. In other words, if the date reported is 11/23/2013, then the case number must have 327 in the middle, because the Julian Date for 11/23/2013 is 327.

    Since the Case Number and the Date Reported are entered at the same time, I want to validate the Julian Date against the "Middle Three" of the case number when the Submit button is pushed, to make sure the user is entering the correct value.

    How would I go about doing that?
    Attached Files
    Last edited by Rich Hartnett; 11-24-2013, 12:56 AM.
    Sergeant Richard Hartnett
    Hyattsville City Police Department
    Maryland

    #2
    Re: Help with Validation of Masked Field

    Code:
    dim date_entered as d
    dim case_number as c = "13-327-0050"
    dim mid_value as n
    dim ord_date as n
    date_entered = {11/23/2013}
    mid_value = val(word(case_number,2,"-"))
    ord_date = jdate(date_entered) - jdate(ctod("1/1/" + year(date_entered)))+1
    if mid_value = ord_date
    	msgbox("Information","The case number is accepted")
    	else
    	msgbox("Warning", "the case number is invalid")
    	end if
    something like this?

    on the webside a javascript alert box can be used for on change event or any other event that seems appropriate.

    Code:
    	dim date_entered as d
    	dim case_number as c
    	dim mid_value as n
    	dim ord_date as n
    	date_entered = e.dataSubmitted.date
    	case_number = e.dataSubmitted.case_number
    	mid_value = val(word(case_number,2,"-"))
    	ord_date = jdate(date_entered) - jdate(ctod("1/1/" + year(date_entered)))+1
    	if mid_value = ord_date
    	validate_case = "alert('The case number is accepted');"
    	else
    	validate_case  = "alert('The case number is invalid!');"
    	end if
    for the webside using dialog.

    if you want, you can assign the case number in the dialog.
    if you have three fields:
    date, incident number and case number
    when you fill in the date and the incident number the case number can be calculated via on change event, ajax call back to have proper case number, thus obviating the need for validation. unless if you must.
    and you can disable the control so no one can change.

    here is something to consider:
    Code:
         dim case_date as d
    	dim yy as c
    	dim ord_date as n
    	dim case_prefix as c
    	dim incident_number as n
    	
    	incident_number = e.dataSubmitted.incident_number
    	case_date = e.dataSubmitted.date
    	yy = substr(alltrim(str(year(case_date))),3,2)
    	ord_date = jdate(case_date) - jdate(ctod("1/1/" + year(case_date)))+1
    	e._set.case_number.value = yy+"-"+ord_date+"-"+incident_number
    Last edited by GGandhi; 11-25-2013, 07:30 AM. Reason: assignment added
    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

    Working...
    X