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



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


  • Filter
  • Time
  • Show
Clear All
new posts


    What I am trying to accomplish is a formula for a payroll

    The employee will make a certain amount per hour depending on how many sales he or she gets that week....

    each record is a weeks payroll sheet

    in the HOURLYRATE field would be a calculated field
    looking for a number in the NUMSALES field

    so if numsales has a 1 in it
    hourlyrate should calculat to 10

    if numsales had 0 in it then hourlyrate should calculate to 8

    if numsales had a 3 in it then hourly rate should calculate to 15

    I wish to do this so the user does not have a chance to mess up the hourly rate, only the number of sales.... etc ..

    Thank you so much for all your help

    Samer N. Gorial

  • #2

    Maybe this will put you on the right track. The following is a nested
    IF statement.

    Field rule for HOURLYRATE field.


    The 8 is the default value that is used when none of the IFs are true.

    Edwin Spencer


    • #3

      The following worked for me as the field rule calculated expression for the HOURLYRATE field. It all goes on one line.



      • #4

        Excellent! Thank you!

        It works great....

        I guess I did not and still dont understand the reason for the 0 in the first string there?

        What exactly does the 0 in """CASE(0, """


        • #5

          how many instances are you trying to deal with?

          The stack overflow is a limitation without a patch as far as I know, but there are other approaches to dealing with what you want to do that don't share that problem.


          • #6

            0 is the default value if the conditions in the CASE statement are not met.


            • #7
              RE: IF NUMSALES=3 HOURLYRATE=9

              I was only trying to place 10 instances or so....

              when I dropped down to 8 it worked fine???

              Anyway... we will stick to eight I guess.. I was just wondering why it seems limited?

              Now I am having a granular crash everytime I try to view a form with tabed subforms...

              it was working fine till I created the fifth tab and started changing colors... I have reduced tabs and I still crash as soon as I try to view... I can view other forms with no trouble, I can move around the main menu with no problem, as soon as I try viewing through the tabed subform I crash.. this happens in both versions a4v5 and a4v7 ??

              I will research the documentation on granular crashes, I have noticed them on the website once while browsing.

              Thank you for your help

              Samer N. Gorial


              • #8
                RE: IF NUMSALES=3 HOURLYRATE=9

                There are 2 more methods you could use. Both methods require you to create a new database that contains 2 fields, numsales and hourlyrate. Use it as a lookup table in 1 of 2 ways. The first method is to use xlookup in your calculated field rule expression. Match the numsales value to the one in the lookup database and pull in the corresponding hourly rate. The second method requires you to create a set which links your data entry database to the lookup database as a 1:1. Link via the numsales field. Pull in the hourly rate value from the child database.