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

Force field value based on another field

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

    Force field value based on another field

    Given two fields, SingleRate and FamilyRate.

    User can enter any value she wants to into the SingleRate field, however, the Family Rate MUST be greater than or equal to the SingleRate. So, if somebody enters 100 in the SingleRate then 50 in the FamilyRate, I'd like the form to automagically overwrite the 50 with 100 in the FamilyRate field.

    If, on the other hand, she enters 200 in the FamilyRate field, the form should accept that and keep the value.

    The default value in FieldRules isn't doing it. Is there another place in the Field Rules I should look at, or must I enforce this rule at the Form level with an event script? If so, which event should I look at?

    Or should I set minimum values for the FamilyRate in the Field Rules and then a Custom Validation with an error message forcing the user to change the value manually? (Personally, I'd prefer the automagic route, but if that's not possible, I'll go the error message route...)
    Lawrence Fox
    ComputerWizard Consulting
    http://www.computerwizardonline.com
    Bookkeeping, Accounting & Database Design
    "Nobody goes to work for themselves in order to do paperwork--so call the Wizard today and get back to doing what YOU love to do..."

    #2
    I'd put the validation on the OnSave event of the form.

    Comment


      #3
      You could also try the OnDepart event of the FamilyRate object on the form. Test for:
      Code:
      If FamilyRate.value < SingleRate.value
         Msgbox to advise user of change
         FamilyRate.Value=SingleRate.value
      End If
      You should also investigate the CanWriteField field event in field rules and the use of the system variable 'A_FIELD_VAlue'. Look under 'Field rules, field events' in the help index. There are some good examples there.
      Tim Kiebert
      Eagle Creek Citrus
      A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

      Comment


        #4
        Tim, is there a way to get field events to work on components (i.e. in contrast to forms)? Thanks and sorry for taking this a bit off-topic.

        Comment


          #5
          Phil,

          Not sure what you are referring to by 'Components'. But if you mean components as in WAS related I have no idea, sorry. I have as yet no experience with that side of A5. You would have better luck posting in one of the WAS forums.
          Tim Kiebert
          Eagle Creek Citrus
          A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

          Comment


            #6
            Tim:

            Put in the OnDepart form event, and it works a treat! Thanks.

            Tom:

            I like my error messages to appear as soon as possible, so I'd rather have it at the field level instead of the form level, e.g., tell the user right away instead of letting her fill in all the fields and then forcing them to go back and "correct" a problem before saving.
            Lawrence Fox
            ComputerWizard Consulting
            http://www.computerwizardonline.com
            Bookkeeping, Accounting & Database Design
            "Nobody goes to work for themselves in order to do paperwork--so call the Wizard today and get back to doing what YOU love to do..."

            Comment

            Working...
            X