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

Why would calculated field give error in expressionbuiler?

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

    Why would calculated field give error in expressionbuiler?

    Good day,

    Refer to the attached screen captures.

    I have entered an expression in the expression builder, which I think should be OK. But A5 is complaining, can you maybe tell me what is wrong? I also attached the screen capture, showing calculated variables after pressing F5.

    Kind regards
    George

    #2
    Re: Why would calculated field give error in expressionbuiler?

    You can't assign a value to a calculated field, other than the calculation which defines the caluclated field. The expression you have in the expression builder should evaluate to true or false if everything else is data typed correctly.
    There can be only one.

    Comment


      #3
      Re: Why would calculated field give error in expressionbuiler?

      Argh! Sorry I messed it up when I tried to prepare the example. Here it is again.

      Comment


        #4
        Re: Why would calculated field give error in expressionbuiler?

        Note that in the left portion of the expression builder where you are defining the expression for the conditional object, calculated fields is not in the list. Must be that the calculated fields are not available in this context.

        You should be able to define the condition for the conditional object using the background calculation(s) for the calculated field.
        Last edited by Stan Mathews; 01-12-2009, 10:34 AM.
        There can be only one.

        Comment


          #5
          Re: Why would calculated field give error in expressionbuiler?

          Hmmm, yes I see. Thanks Stan.

          Kind regards
          George

          Comment


            #6
            Re: Why would calculated field give error in expressionbuiler?

            Hi George the syntax for your calculated field would need to be along the lines of

            calc_points = if(totalpoints>9,totalpoints,0)

            That would populate the field with the value of totalpoints if totalpoints is more than nine and zero otherwise.

            Another example for your reporting might be

            calc_points = if(totalpoints>9,"You have earned "+ltrim(str(totalpoints,6,0))+" points","")

            the above would return a character string as the calculated field value as follows.

            Assuming the value in the in the totalpoints field is 21 the calculated field would display as

            You have earned 21 points

            If it were 8 the calcuated field would be empty.

            Regards
            Bob
            Bob Whitaker

            Comment


              #7
              Re: Why would calculated field give error in expressionbuiler?

              Thanks Bob, you guys have really made a difference. Today I closed a bug (in my app) which was logged by the customer 1 month ago, but I had no idea how to fix it.

              Thanks
              George

              Comment

              Working...
              X