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

Custom Validation

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

  • Custom Validation

    I have the following line in the custom validation for the fields, Gamedate, Time, and Field_num. The code is to check for duplications of the three fields.

    .NOT.KEY_EXIST("GameValid",CDATE(GameDATE)+TIME+STR(FIELD_NUM,4,0))

    The code works fine during an enter. However, if I try and do a change of data, when I do a save F9, I get a FIELD VALUE NOT VALID error. Any ideas of what it will take to make this work?

    Thanks

  • #2
    RE: Custom Validation

    Try moving your expression from, I assume, a table level field rule, to a form level field event such as CanArrive.

    Check the mode, change or enter, and if in enter mode, allow the entry, if in change mode, give focus to the next field in the tab order. Then do the same in the CanDepart, but now if in enter, perform the validation, if in change, just allow the change

    Should work.
    There can be only one.

    Comment


    • #3
      RE: Custom Validation

      Stan,

      I need the validation check in the change mode if they change any of the three fields in question: gamedate, time,field_num.

      Currently if I enter a record and there is a duplication based upon the Gamedate index, I get a validation error (this is correct), I change the data (during the enter) that is causing the duplication and I can save the record.

      If I come back to the record and try to change any field, not just the three for the validation rule, after I change data in a field and hit F9 is when I get the error.

      You are correct, the code is currently stored in the table field rules for all three fields. I can put the code on only one field and the problem still exists.

      Comment


      • #4
        RE: Custom Validation

        Try putting the validation code only on the last field to be entered (tab order). And if you "require" in field rules the other two rules so that they cannot get by them if they are blank. Then cross your fingers and give it a try...but I find the crossed fingers difficult to type with.

        Good Luck

        Tom

        Comment


        • #5
          RE: Custom Validation

          "If I come back to the record and try to change any field, not just the three for the validation rule, after I change data in a field and hit F9 is when I get the error."

          I think that when the field rule fires from the table level field rules, on entry you are ok because either the key does not exist or it prevents you from creating a duplicate.

          On the other hand, when you try to make a change anywhere in the record, and commit the change, the field rule fires again and now the key does exist......for this record. The key_exist function tells you if the index key value exists anywhere, not just in some other record.
          There can be only one.

          Comment


          • #6
            RE: Custom Validation

            This sounds just like the validation rule switch problem from 4.02 to 4.03 that is described in the readme403.pdf

            You'll need to stop using key_exists and use key_unique instead.

            Finian
            Finian

            Comment


            • #7
              RE: Custom Validation

              Phil:

              (Stan, please check me on this.)

              I believe you are hanging up on the difference between key_exist and key_unique which came in with version 4.03. Check page 31 of the 4.03 doc.

              The change is that starting with 4.03 field rules are reevaluated on change. When you enter the record you are ok, but when you change it, the key already exists so your validation fails.

              The documentation instructs you to substitute
              key_unique(key_expression)
              for
              .not.key_exist(key_expression)

              Bill
              Bill Hanigsberg

              Comment


              • #8
                RE: Custom Validation

                Bill,

                You are correct. I found the reference to key_unique(), but Finnian got there first.

                Thanks,

                Stan
                There can be only one.

                Comment


                • #9
                  RE: Custom Validation

                  Wouldn't it be "nice" if Alpha redid the online documentation to reflect the current set of xbasic commands, instead of us having to search several documents to find the needed command?
                  There can be only one.

                  Comment


                  • #10
                    RE: Custom Validation

                    Finian,

                    Thanks, I would have never found the new command without your message. I just changed the validation rule and the initial indication is that everything works fine with the key_unique command. In addition, the format is simpler.

                    Once again, thanks
                    Phil

                    Comment


                    • #11
                      RE: Custom Validation

                      Thanks to all, especially to you Phillip for asking the question. I just fixed the same problem, but would like
                      to add (for the next poor slob unfortunate enough to
                      come across the same probelm) that the parameter list for the key_unique function does not include the key value,
                      only the reference to tagname (index) is needed.

                      Again thanks to all, said it before, and I'll say it again
                      without this forum, I'm dead.

                      With some 65 thousand hits on this thing (a5 forum) what can it mean ???? ..... hmmmmmm, maybe the pooorest documentation ever? Nah, just being facetious.

                      Comment

                      Working...
                      X