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

case statement in field rules

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

    case statement in field rules

    Hi Everyone!

    I am trying to set a numerical default value using a simple expresion as follows:

    case(SPECIAL->Price>0,SPECIAL->Price,
    CUSTOMER->Price_Level=10,PRICE->Price_10,
    CUSTOMER->Price_Level=9,PRICE->Price_9,
    CUSTOMER->Price_Level=8,PRICE->Price_8,
    CUSTOMER->Price_Level=7,PRICE->Price_7,
    CUSTOMER->Price_Level=6,PRICE->Price_6,
    CUSTOMER->Price_Level=5,PRICE->Price_5,
    CUSTOMER->Price_Level=4,PRICE->Price_4,
    CUSTOMER->Price_Level=3,PRICE->Price_3,
    CUSTOMER->Price_Level=2,PRICE->Price_2,
    CUSTOMER->Price_Level=1,PRICE->Price_1)

    When I go to save the field rules after adding this I get an unhandled exception error. Then when I restart A5 a lot of my field rules are gone. I can get it to work with a nested IF statement however.

    Any thoughts, Dan
    Tags: None
    #2
    RE: case statement in field rules

    Well I've played around with this a little and can add the following information: this works

    case(SPECIAL->Price>0,SPECIAL->Price,
    CUSTOMER->Price_Level=10,PRICE->Price_10)

    However as I add more conditions, it stops somewhere along the way. Also I lied about the nested if statement, it works up to five levels and quits.

    The complete statement does return a result in the expression builder window and allows me to leave to go to other fields, the unhandled exception does not occur until I go to save the field rules or more specifically when I go to close the field rule editor it asks if I want to save and crashes when I answer yes.

    I have now tried this on two machines, both running XP Home. I have 1420-1037 on one and 1330-1018 on the other (A5 versions).

    I have already tried compacting and also duplicating all the databases to replace the existing ones.

    I am editing field rules for a set. What I dont get is why the statements work for 4 0r 5 conditions but not the full set of conditions.

    Thanks for any input, Dan

    Comment

      #3
      RE: case statement in field rules

      Dan,

      Can't see your actual expression, but it's supposed to be on one long line, unless you use the line continuation character to break them...

      If you're inserting carriage returns or line fields by pressing the enter key that may explain what you're seeing.

      -- tom

      Comment

        #4
        RE: case statement in field rules

        Hi Tom,

        Actually it is on one long line, but when I pasted it here it made it hard to read so I formatted it for clarity, guess that was not a good idea.

        Comment

          #5
          RE: case statement in field rules

          Dan,

          Actually, breaking the lines so we could read them more easily was a big help.

          You mention this is for a set. Are you defining a default value for a child table, using a value from the linked primary record? Until someone can explain what's happening you might try storing the customer's price level in the child table record first, and then using that field to do your comparisons. This could be done at the form level, instead of in field rules at the table level. Perhaps that will suffice, especially if your data entry routine will use one principal form.

          Another idea would be to use a lookup() function to retrieve the desired price. This could probably be done in field rules by putting the prices in a separate table, indexing on the pricelevel field, and retrieving the desired price that way.

          Food for thought, even though no specific solution is occurring to me.

          -- tom

          Comment

            #6
            RE: case statement in field rules

            Hi Tom,

            Thanks for the thoughts, your impression is correct, I am setting a default value for a child record using a condition referencing the parent. I'll try moving the condition value into the child record and redo the case statement from that stance, I'll let you know.

            Thanks, Dan

            Comment

              #7
              RE: case statement in field rules

              Hi Tom,

              Alpha 5 liked your suggestion and if it's happy I'm happy!!
              Anyway moving the condition value into the child record fixed my case statement problem, thanks much, Dan

              Comment

                #8
                RE: case statement in field rules

                Dan,

                that's good news.

                In Alpha Five I believe the field rules are designed and saved at the table level, not the set level. This is different from how Alpha Four did it back in DOS. It's my personal practice to design Alpha Five field rules to work as though the table will ALWAYS be manipulated outside of any set. In other words, I never assume that fields in other tables will be 'in scope' when data entry is occuring in the table at hand.

                -- tom

                Comment

                Previous template Next
                Working...
                X