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

Field Uniqueness

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

    Field Uniqueness

    When combining 4 fields for unique validation, and the 4th field is a "default" insert at the beginning of the form, the validation fails. However, if I insert the character manually, it works.

    I don't want the user to have to manually enter the last field, each time. How can I include the 4th field, as a combination of the other 3, and maintain a "default" entry.

    Jim Morris

    #2
    RE: Field Uniqueness

    Huh? What youo've said is pretty vague and could probably be intrepreted differently by different folks.

    How about showing us your script and explain where it's placed. That's much easier than trying to figure out what you mean.


    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    Comment


      #3
      RE: Field Uniqueness

      instead of a default field rule, you might try having a script on the "On Enter" event of the form. Something like "Appt_date.value = date()". I don't know if this will fix your problem. but it's easy to try.

      Comment


        #4
        RE: Field Uniqueness

        Origin_Booking_Station+Destination_Port+Booking_Number+Suffix

        Ken, above are the four fields which are combined to create a "unique" combination that should not be dupliated. The last field, "Suffix", is currently set to "default value" of "A".

        The purpose would be, if fields 1/2/3 combined with the default value of A, create a duplicate on entry, we change the suffix to B, thus allow us to know there is another one in the database. Additionally, when the second one is called up and printed on a manifest of items, we again know, this is the second time it has appeared.

        The combination of the 4 fields work fine, if the user inputs the value of A manually. If, however, the system enters the default value of "A", then the combination does not appear unique to the software.

        I hope this helps. Thanks

        Jim Morris

        Comment


          #5
          RE: Field Uniqueness

          You can set the default "A" at the beginning or end of data entry. If it is set at the end (when the record is saved) it may not get read correctly?

          Just a thought...

          Comment


            #6
            RE: Field Uniqueness

            Jim, I had the same thought as Stephen.

            When is 'uniqueness' determined? If it's happening before the default value is supplied to the fourth field, you'll get the problem you are seeing. Check the default field rule for the fourth field and see if checkin the box to force alpha Five to fill it in at the beginning of data entry solves your problem.

            -- tom

            Comment


              #7
              RE: Field Uniqueness

              Thanks Tom

              The field is set as default "at start of entry", so when the form first opens, the "A" is inserted before any data is entered.

              Any other ideas?

              Jim Morris

              Comment


                #8
                RE: Field Uniqueness

                Jim, yes. Post a sample that illustrates the problem here.

                -- tom

                Comment


                  #9
                  RE: Field Uniqueness

                  I would also suspect that the uniqueness is being determined ahead of the default rules assignment. This would happen especially if uniqueness is determined at a database engine level of assignment (I.E. first). Would changing this last field to a calculated and incremented field type be an improvement?

                  Dave

                  Comment


                    #10
                    RE: Field Uniqueness

                    BINGO!

                    That's the answer. "When" the engine decides the field is unique. I changed the association on the 3rd field, instead of the 4th (and last, which is also the default), and it works fine. If, by the third entry, if the combination of the 4 are a duplicate it stops. I have to delete the 3rd field, change the 4th (suffix code), and then backup and reneter the 3rd, and it works.

                    For the amount of times we should hit the suffix, or duplicate, the process is not that unbearable, and it certainly accomplishes our goal.

                    Thank you very much!!!

                    Jim Morris

                    Comment

                    Working...
                    X