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

calculated field in a report

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

    calculated field in a report

    hi folks, i'm trying to create a field that is filled in the report depending upon the data in other fields; i.e: i've created a calculated field in the details section called CODE.if the field TY has "m" and field R_BK isblank, then CODEfield is "fl". i wrote it in the expression builder as: if(isblank("R_BK").and.TY="f","fl") the evaluation responds 'to few parameters'. am i even in the correct application(calculated fields)? there are a number of combinations for the CODE field. do i keep reentering for each combination of R_BK/TY? i don't underestand the if condition; where does the 'then' get entered? thanks, david

    #2
    RE: calculated field in a report

    David,

    Should read as
    if(isblank("R_BK").and.TY="f","fl","")
    You did not finish the code
    Try reading the help

    Dave

    Comment


      #3
      RE: calculated field in a report

      "...if the field TY has "m" and field R_BK isblank then code field is FL." But what if the condition is not met. What should the code field be then. If code should be nul (blank) except when the condition is met then try

      if(isblank("R_BK").and.(TY="m"),"fl","")

      if code should be something else when the condition is not met then

      if(isblank("R_BK").and.(TY="m"),"fl","something else here")

      While we are at it, I wouldn't like to have a field named "code" as it could lead to problems.

      Bill
      Bill Hanigsberg

      Comment


        #4
        RE: calculated field in a report

        thanks superdave

        Comment


          #5
          RE: calculated field in a report

          hi william, thanks. i agree and will change the field name.do i keep listing the IF expressions;i.e: if TY is: "m" ,"t","s","w", and R_BK is isblank or isnotblank for each combination of TY and R_BK the CODE field will have a different result. do i just keep making a really long expression or do i enter one, then go back and start a new expression for the next combo? thanks, david

          Comment


            #6
            RE: calculated field in a report

            If you have 16 or less combinations, the CASE function would work well here.

            Comment


              #7
              RE: calculated field in a report

              hi ohlen,the only thing i've found on CASE is on pg.219, where do i find more info on how to use it? much thanks, david

              Comment


                #8
                RE: calculated field in a report

                David:

                From the help files, also xbasic doc pg. 120:

                Bill


                SELECT ... CASE

                Syntax:

                SELECT
                [CASE Logical Expression1
                [Statements1] ]
                [CASE Logical Expression2
                [Statements2] ]
                ...
                [CASE Logical ExpressionN
                [StatementsN] ]
                [CASE ELSE]
                [StatementsE] ]
                END SELECT


                Description:

                A conditional control structure comprised of one or more CASE statements. The Logical Expression of each CASE statement is evaluated until a TRUE result is reached. The statements for the TRUE CASE are executed, and program flow continues after the END SELECT. The statements listed after the CASE ELSE are executed as the default action if no other CASE expression is TRUE.

                Examples:

                'Associate a grade with a score. Any score below 60 is an F.
                '-----------------------------------------------------------
                FUNCTION test_grade AS C(score AS N)
                SELECT
                CASE score >= 90
                grade = "A"
                CASE score >= 80
                grade = "B"
                CASE score >= 70
                grade = "C"
                CASE score >= 60
                grade = "D"
                CASE ELSE
                grade = "F"
                END SELECT
                test_grade = grade
                END FUNCTION
                Bill Hanigsberg

                Comment


                  #9
                  RE: calculated field in a report

                  thanks bill; i'll give it a go ! david

                  Comment


                    #10
                    RE: calculated field in a report

                    Bill,
                    This is a good explanation of the Select-Case X-basic statement. I was thinking of the case function.

                    case(condition1,expression1,condition2,expresion2, etc,etc)

                    I found the explanation on page 371 of the online manual.

                    See you in 2 weeks.

                    Comment


                      #11
                      RE: calculated field in a report

                      Very true; I got turned around on this.

                      At this conference let's not pass each other like strangers in the night!

                      Bill
                      Bill Hanigsberg

                      Comment

                      Working...
                      X