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

if().OR.IF() causing calc. field problem

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

    if().OR.IF() causing calc. field problem

    When I set up a calculated field as follows, it returns the correct answer including the correct decimal places:
    if(field#1="lab",numericField#2,0)

    However, if I attempt to add an .OR. function to this, the calculation returns an answer which has disregarded my decimal places.
    if(field#1="lab",numericField#2,0).OR.if(field#2="lab",numericField#3,0)
    For some reason, this second equation drops my decimal places and returns the next lower whole number. This may not matter when it's 99cents, but if I multiply by a thousand it is wrong by $990.
    I have already made sure that all of my numeric fields do contain decimal places; none of them are whole numbers alone. What's up? How can I fix this?

    #2
    RE: if().OR.IF() causing calc. field problem

    Using booleans/ logical operators can end up with results othere than you expect sometimes (if it's false or false then its true, or something like that). Sometimes I hate booleans.

    Instead of
    if(field#1="lab",numericField#2,0).OR.if(field#2="lab",numericField#3,0)
    try putting the IF after the .OR. into the false portion of the first IF (and add 2nd close parenthesis:
    if(field#1="lab",numericField#2,if(field#2="lab",numericField#3,0))
    Assuming I didn't type it wron, since numericField#2 evaluates .F. the false condition, now the second IF is executed. If it evaluates .F. then the false condition of the second IF is returned.

    Comment


      #3
      RE: if().OR.IF() causing calc. field problem

      Your expression does not result in a single logical result.

      if(field#1="lab",numericField#2,0).OR.if(field#2="lab",numericField#3,0)


      To force a single return value shouldn't it be:


      if(field#1 = "lab" .or. field#2 = "lab", if(field#1 = "lab",numericField#2,numericField$3),0)


      -- tom

      Comment


        #4
        RE: if().OR.IF() causing calc. field problem

        you're performing an "or" operation on 2 numeric fields, one of which
        probably always evaluates to 0, so, for example:

        ? 3.8 .or. 0
        = 3.000000

        ? 1.999 .or. 0
        = 1.000000

        Comment


          #5
          RE: if().OR.IF() causing calc. field problem

          Really wanted your answer to be right! But when I added decimals to the zero, the calculation still failed to pick up my decimals. In the end I've added a new set of fields to deal with the second set of possibility. Thanks.

          Comment


            #6
            RE: if().OR.IF() causing calc. field problem

            after my initial reply to Peter Wayne, I tried Jim Rowlen's solution again and - his works not only for the 2 sets of possibilities I mentioned but it works when expanded to include four sets. Thanks to everyone who replied.

            if(field1="lab",field2,if(field3="lab",field4,if(field5="lab",field6,0))) etc.

            Comment

            Working...
            X