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

Problem with UNIQUE field rule

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

    Problem with UNIQUE field rule

    I want to prevent an operator from entering a duplicate part number in an inventory program. Since the same part number is available from more than one vendor, that complicates things.

    So: I created a calculated field: I called it "part_id" and the calculation is alltrim(str(vendor_Id))+alltrim(PN). This should create a unique string of vendor_ID plus part number (PN). Part_ID is created successfully, no problem.

    My problem is, when I go to "Validations" in field rules, the Uniqueness test option is grayed out and I can't select it. I could swear I could do this before but it certainly isn't available to me now. How do I make the program test to see if my "partid" is unique?
    Jim Belanger

    #2
    Re: Problem with UNIQUE field rule

    How would the calculation expression be handled if it wasn't unique? Go back and start over and recalculate? As you can see, a uniqueness expression for a calculated field makes no sense.

    Choose one of the two parts of the expression

    alltrim(str(vendor_Id))+alltrim(PN)

    and enter a validation expression for it. Value of Expression must be unique, and enter the expression for the calculated field.
    There can be only one.

    Comment


      #3
      Re: Problem with UNIQUE field rule

      Duh. OK, I see what you mean. Does it matter which part of the expression I use? Should it be the second one to be entered? I suppose so, otherwise the program can't test the validation equation. I don't have to have this test on the onsave event, do I? Yeah, I know - Come on Jim - Try it and see!!! I'll put it on the Vendor ID field which is a lookup from Vendor Name and "Must Exist" in Vendor table. Thanks for pointing me in the right direction.
      Jim Belanger

      Comment


        #4
        Re: Problem with UNIQUE field rule

        Nope
        Put that uniqueness test on Vendor_ID field and I could still enter a duplicate part number from the same vendor.
        Jim Belanger

        Comment


          #5
          Re: Problem with UNIQUE field rule

          Use the whole expression. I'm uncertain which field you should use. Do you mean to say that you can't allow the same part number from two different vendors? That doesn't seem right.
          There can be only one.

          Comment


            #6
            Re: Problem with UNIQUE field rule

            I want to allow the same part number from two different vendors. I want to prevent the same part number from the same vendor from being entered.
            Jim Belanger

            Comment


              #7
              Re: Problem with UNIQUE field rule

              As soon as I put that expression on the Vendor Name field, it won't allow me to enter that vendor again, no matter what the part number is. I also tried key_unique("part_id") and key_unique(alltrim(str(vendor_Id))+alltrim(PN)) and those didn't work either.
              Jim Belanger

              Comment


                #8
                Re: Problem with UNIQUE field rule

                OK, I think I've figured it out.
                If I go in Field Rules and don't specify a unique rule but go to "custom Validations" and there I enter key_unique("part_id") with a message that says PN & Vendor Exists; I am allowed to enter a duplicate until I try to save the record. Then, I get the error message "PN & Vendor Exists". I hope this works without unseen glitches.

                Thanks for the help.
                Jim Belanger

                Comment


                  #9
                  Re: Problem with UNIQUE field rule

                  Probably better use a custom validation.

                  Define an index named alltrim with the expression

                  alltrim(str(vendor_Id))+alltrim(PN)

                  Create a custom validation in the field rules for the pn field.

                  Validation------------------------------------------------------------Message
                  .NOT. EXIST(ALLTRIM(STR(VENDOR_ID))+ALLTRIM(PN),"test","alltrim")--"Can't do that."

                  Use your tablename instead of test.
                  There can be only one.

                  Comment


                    #10
                    Re: Problem with UNIQUE field rule

                    When I went to the Indexes part of Field Rules, there was already an index there called "alltrim" and with the same definition. Anyway, I did exactly what you said and put it on the PN field and it works fine. Thanks again.
                    Jim Belanger

                    Comment


                      #11
                      Re: Problem with UNIQUE field rule

                      I spoke too soon. That cure prevented the entry of a duplicate part/vendor combination but, it would not allow any editing of an existing record. When the operator went to save the edited record, they got the message that it was a duplicate. So, I went back to the Key_unique function and I got that to work OK.
                      Jim Belanger

                      Comment

                      Working...
                      X