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

OnDepart field event

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

    OnDepart field event

    I have a situation with side by side fields with an on depart field rule. The first rule works fine if no rule has been defined for the second field, the field that is next in the tab order. When you define a rule for the second field, the cursor will just toggle between the two fields, and neither field can be entered. You have to exit Alpha 5 and restart.

    Is this a program bug? Is anyone else having this problem?

    If you need the program this happening in, I will be happy to send it.

    I have the most recent update of Alpha 5.

    Thanks,
    Chuck

    #2
    RE: OnDepart field event

    Chuck,

    Yes, please attach a working copy of the database so others can verify the behavior you're reporting, and possibly offer suggested solutions. -- tom

    Comment


      #3
      RE: OnDepart field event

      I am sending to zip files. The first is with the "Total wager this race" OnDepart field rule defined. Enter a new record and when you come to this field, enter 0, or 1, you will notice a message pops up telling you to use any number equaled to 2 or more. Enter 200, press enter, the cursor moves to the next field. Wa La, that is right.

      Unzip 2field zip. Now enter a record, just as you did last time. When you come to the "Total wager this race", enter either 0, 1. press enter. The cursor gets all tangled up. This is the problem. Is this me or the program?

      Your help in this matter is appreciated.

      Best Wishes,
      Chuck

      Comment


        #4
        RE: OnDepart field event

        Here is the 2field zip file

        Comment


          #5
          RE: OnDepart field event

          I believe you should rethink your logic and event choice.

          Currently you

          get the data entry for the "total_wager"
          activate the wager type field
          conditionally display a message if the amount in the total_wager is incorrect
          .....all when the cursor departs the total_wager field

          maybe you should

          get the data entry for the "total_wager"
          display a message if the amount in the total_wager is incorrect and return the cursor to the total wager field
          (accomplished by using the candepart event, not the ondepart

          then if the wager type field is next in the tab order you don't even need to use code to activate it.

          You could also use the candepart for the wager type field, or make it required in the table field rules, or make it a lookup field.....

          BTW, your test for wager amount "display a message if the amount in the total_wager is incorrect" - would seem to make more sense to me as "Total_Wager"2". What happens in your test if the user enters "-4"?
          There can be only one.

          Comment


            #6
            RE: OnDepart field event

            Charles

            In addition to Stans comments, the reason the cursor jumps back and forth is because your first action on the OnDepart is to activate the next field. When the code sends focus back to the original field, the second objects OnDepart fires, which starts the loop. Remove the activate() command as it isn't needed. Just set your tab order to the correct order.

            As Stan points out, if you want to test a value use the CanDepart and cacel if the condition is not met. Then focus never leaves that object.

            Jerry

            Comment

            Working...
            X