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
Devcon 2020 Goes Virtual! LEARN MORE >

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

prevent double entry

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    prevent double entry

    I have a form with a button that enters data in a subform with a one to one link.I want to stop the action if the user
    attempts to enter the same data again. I am entering the stats from a baseball game. The game has a field GAME_ID. There should only be one GAME_ID per player. GAME_ID is also set to a variable. VAR->GAME_ID. I would like to have a message pop up on the button that attempts to initiate an entry into the subform. Something like: "This player has already been entered". Action scripting is best for me. Very limited with xbasic. I tried field rules but it seemed to stop the entry based on uniqueness in the entire table.
    Thank you,
    Bob
    Tags: None
    #2
    RE: prevent double entry

    Your field rule attempt probably stopped the action based on table uniqueness because you built it on the value of the value of the field itself.

    The next lower choice in the uniqueness test is "value of expression". Try creating a uniqueness test based an expression like game_id + playerid.
    There can be only one.

    Comment

      #3
      RE: prevent double entry

      Thanks Stan,
      Works good. Now the problem is the GAME_ID field on the sub form stays blank. It is set to default var->game_id in the field rules. Have I created a total mess?
      Bob

      Comment

        #4
        RE: prevent double entry

        Stan, I have changed my mind. I would like to use the action on the button. I will place a branch to display a message if game_id is the same as var_game_id. The problem I have is with the expression builder. It evaluates when I check it but when I hit OKI I get a message saying..."Must evaluate to a character string" Here is the expression on the branch in the action scripting. Batting->Game_Id=Var->Game_Id
        Looks like a charactrer to me.
        Thanks
        Bob

        Comment

          #5
          RE: prevent double entry

          We didn't change anything that should have affected the display of the game_id field on a subform.

          You say "It is set to default var->game_id in the field rules." I'm not sure I understand. Do you mean that there is code on the button to store the current var->game_id to the game_id field if the uniqueness test is passed?

          In any case you probably need to refresh() the subform display to show the change.
          There can be only one.

          Comment

            #6
            RE: prevent double entry

            Bob,

            Try evaluating

            Batting->Game_Id=Var->Game_Id

            in your head.

            If you come up with an answer other than true (.T.)or false (.F.), please explain. Not a character expression.

            Where are you using the expression?
            There can be only one.

            Comment

              #7
              RE: prevent double entry

              Sorry, I see the situation now.

              You need to branch based on "value of a control" rather than value of an expression is you wish to proceed as stated and I'm not sure you can compare two controls (var->game_id and "field" game_id) through action scripting.
              There can be only one.

              Comment

                #8
                RE: prevent double entry

                Thanks Stan,
                I will give it a try though. I can get enough xbasic to make an attempt. That may have put me in the right direction.
                Bob

                Comment

                  #9
                  RE: prevent double entry

                  Ok I'm back to the field rules. I can get it to work ok. Is there any way to have a custom message instead of the one that Alpha displys? In order to get out of the field if it is not unique the user has to use rightclick to cancel.
                  Thanks again,
                  Bob

                  Comment

                    #10
                    RE: prevent double entry

                    What you really want is a custom validation.

                    Define an index on game_id + player_id (tagname = combo), assuming that's how your fields are named and that they are both character.

                    Now go back to the field rules, delete the uniqueness test from before, fill in a custom validation:

                    key_unique("combo")

                    and enter your desired custom message (put quotes around the text of your message in the definition).
                    There can be only one.

                    Comment

                      #11
                      RE: prevent double entry

                      Thank you! Thank you! Thank you! Works perfect!

                      I noticed another post talked about earning a living with A5. Am I going to get a bill?
                      Thanks again,
                      Bob

                      Comment

                        #12
                        RE: prevent double entry

                        Not from me.

                        This is how I learn, and remember.
                        There can be only one.

                        Comment

                        Previous template Next
                        Working...
                        X