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

Accuracy of calculated fields upon data entry

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

    Accuracy of calculated fields upon data entry

    I've got a data structure that has three monetary fields. The first is Netto (German for net value), Steuer (Tax) and then Brutto-- representing net value minus the tax. The calculation rules are:

    Netto (manually entered)
    Steuer = Netto-(Netto/1.16)
    Brutto = Netto-Steuer

    A typical (and correct) calculation would be:

    Netto = 116.00
    Steuer = 16.00
    Brutto = 100.00

    My problem is that after manually entering the netto value, the steuer value is correct, but the Brutto is incorrect. It seems that somehow it is picking up previous values of the Netto field.

    For example, if I enter a completely new record, the values are, respectively, 116, 16 and 116 after I manually enter Netto. The last value should be 100. If, however, I go to a previous record, or I add a new one, the value Brutto is updated correctly.

    This outcome is the same whether I am using a table (browse) or form to enter the data.

    My question: if the second field (calculation field) is calculating correctly upon my manual data entry, why isn't the last field calculating correctly?

    My only hunch on this is that the last calculation field happens to be the very last field of the form, and this may be "causing" the problem.

    What can I do to ensure that the value I'm getting is automatically correct (and calculated) when the first value is manually entered--without having to procede to a new or previous record?

    -- John


    Tags: None
    #2
    RE: Accuracy of calculated fields upon data entry

    John,

    What expression did you use and how did you use it? In a calculaed field defined in the field rules or a calculated field from the Drag/Drop list?

    If you had a calculated field called Brutto, the expression would be:

    Netto-(Netto-(Netto/1.16))

    I think that will work.

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    Comment

      #3
      RE: Accuracy of calculated fields upon data entry

      Say Kenn, you were really slow on that. I mean, be considerate: I sent my question out, and it took you 5 whole minutes to get back to me. I mean, really! I didn't have time to get another cup of coffee!

      ;)

      Goodness! You must have been sitting at the monitor when my note was posted! Thanks! Your formula worked. I was using a calculated field defined in the field rules.

      I'm still not sure why my formula didn't work: I used a manually-input value for a subsequently calculated field--which computed correctly, and then constructed a calculation rule for the next field which subtracted that result from the original manually-entered value.

      With paging, the value computed correctly. It was only when I "stayed" with the values in the form, that the computed result for the last field was incorrect as displayed.

      I'm missing something here. I think I'll have to read the manual more closely on this. (Would there be a special section for this? I've looked, but didn't locate one; maybe I need to use my glasses!)

      Thanks so much Kenn; I really appreciate the fast (and valuable!) response.

      (Say: Won't it be something if the USA wins the soccer cup??!!!)

      Comment

        #4
        RE: Accuracy of calculated fields upon data entry

        John,

        There is a section on expressions that deal with priorities of calculations but I'm not sure where it is as I haven't looked at it in awhile.

        I'll try to be a little more 'Johnny on the spot'; sorry it took so long to answer your request. Ha, you caught me at the right time. Woke up wide awake so thought I'd sit on the computer throne for a bit.

        Anyhow, glad I could be of help.

        kenn
        TYVM :) kenn

        Knowing what you can achieve will not become reality until you imagine and explore.

        Comment

          #5
          RE: Accuracy of calculated fields upon data entry

          Here's another Ken's comments a whole 12 hours later [I slept in]

          The rule for field rule calculations should be...
          don't use the value of a calculated field in the formula for another in the same record. Base each calculated field upon the values of fields that are manually entered.

          Kenn's formula demonstrates that quite well.

          I'm going to bed.

          Ken [the other one]

          Comment

          Previous template Next
          Working...
          X