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

Date Entry Validation

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

    Date Entry Validation

    How do i set in field rules the date validation so that the new date is not later than the last date of the last record.
    for example the last diagnosis date of a patient is 1/2/2012,then the user cannot enter 1/1/2012 or 12/31/2011 or 12/30/2011 and so on...
    Sample Scenario
    Patient No Diag Date
    01 1/2/2012
    01 User cannot input 12/31/2011 here , it must be 1/3/2012 or future

    Another sample would be, on a savings app.the user should not input
    the new transaction date to be later than the last transaction date.Thanks
    Last edited by JetLi; 01-06-2012, 09:18 AM.

    #2
    Re: Date Entry Validation

    Why have them enter the date?

    Set the default expression to date() and set the Skip to .T. in the field rules.

    In the second case you define Validations in the field rules, Custom section.
    There can be only one.

    Comment


      #3
      Re: Date Entry Validation

      I think the solution to this will be finding a good way to identify the "last" record prior to the current one. There are several possibilities.

      Once the correct "last" record is found you could run a script in the CanSaveRecord event in field rules for the table to validate the diagnosis date in the pending record.

      Perhaps someone else will post a simpler suggestion.

      Comment


        #4
        Re: Date Entry Validation

        Originally posted by Tom Cone Jr View Post
        I think the solution to this will be finding a good way to identify the "last" record prior to the current one. There are several possibilities.

        Once the correct "last" record is found you could run a script in the CanSaveRecord event in field rules for the table to validate the diagnosis date in the pending record.

        Perhaps someone else will post a simpler suggestion.
        If this can't be done in a point and click in alpha field rules, then this would be a good suggestion, question is HOW? don't know yet Xbasic.Thanks!

        Comment


          #5
          Re: Date Entry Validation

          Originally posted by Stan Mathews View Post
          Why have them enter the date?

          Set the default expression to date() and set the Skip to .T. in the field rules.

          In the second case you define Validations in the field rules, Custom section.
          Please show how? Thanks!

          Comment


            #6
            Re: Date Entry Validation

            No. You can easily find this in the wiki.
            There can be only one.

            Comment


              #7
              Re: Date Entry Validation

              Jetson,

              You also have to define what you mean by "last record" precisely.

              I presume you mean last record for the particular patient. To figure out how to do this--not the syntax, but the object of the syntax--we would need to know if each clinical intervention with a patient is a separate record or if all interventions for a given patient are stored in a single record (which will give you problems in the long run).

              Perhaps you could post a sample database with nomnative data removed.

              Bill
              Bill Hanigsberg

              Comment


                #8
                Re: Date Entry Validation

                Originally posted by Tom Cone Jr View Post
                I think the solution to this will be finding a good way to identify the "last" record prior to the current one. There are several possibilities.

                Once the correct "last" record is found you could run a script in the CanSaveRecord event in field rules for the table to validate the diagnosis date in the pending record.

                Perhaps someone else will post a simpler suggestion.
                Tom,I think your suggestion is the best way to do it,Dont know how this can be done in Alpha,but I can do it in vb6, before saving the record, i would code a routine to check for the last diagnosis date based on a patient number being currently edited,then after getting that value, i can then compare it to the new date of diagnosis entered by the user,then check if the new date is less than the last diagnosis date, my purpose in doing this is to eliminate the possibility that the user will make an error in setting the diagnosis date,of course in alpha, it is very easy to set the default date so that users will not make a mistake, but sometimes users will encode the diagnosis date at a later time and i don't want users to make a wrong entry on diagnosis date. Tom's idea is the same with me but i don't know how it is done in alpha five.How?

                Comment


                  #9
                  Re: Date Entry Validation

                  Tom actually told you how. He did not write your code for you. Again, this can be found in the wicki as Stan said. Bill gave you a real good suggestion also.

                  You do it basically the same as vb6. Once you learn what an onsave event is, the rest will be easy.

                  By the way, these three are some of, if not the best on this forum.
                  Dave Mason
                  [email protected]
                  Skype is dave.mason46

                  Comment


                    #10
                    Re: Date Entry Validation

                    Thank you!

                    Comment

                    Working...
                    X