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

Calculation problems

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

    Calculation problems

    I have a set with three tables 1. items received 2. items pulled. I have a form that has a starting balance, an embedded browse of all the received and a browse for the pulled. Thus giving me an inventory amount.

    The problem is when the screen is open and changes are made to the two tables the calculations go out of wack. I can try a refresh screen or change records but it is often wrong. Is there a way short of closing down the form and then open it again for it to acknowledge the changes.

    #2
    RE: Calculation problems

    You don't specify where the "inventory amount" field/variable/calculated field exists. Is it a table field on the form, a calculated field on the form, or what?
    There can be only one.

    Comment


      #3
      RE: Calculation problems

      Sorry the third table I referred to contains the id#, description fields, and initial count. The calculated field for the balance amount is a on the form only.

      The calc for balance reads

      (Open_Balance)+(Calc->Tot_Calc_Total_Received_2001)-(Calc->Tot_Calc_Total_2001_Issued)

      The two total fields are totals grouped by the ID#


      I have put the brackets in just now for ease of viewing.

      Comment


        #4
        RE: Calculation problems

        I am concerned with how you are obtaining the values for

        Calc->Tot_Calc_Total_Received_2001
        and
        Calc->Tot_Calc_Total_2001_Issued

        as there has been some discussion of using total() vs dbsum().

        See below.


        Msg ID: 47453
        Subject: WARNING! Calc field using DBSUM vs. TOTAL
        Author: Bill Warner
        Date: 09-13-2001 18:12
        File:

        Cal Locklin and I have discovered that using TOTAL(FIELD1,GRP->FIELD2) as a calc field in a form is NOT always reliable.

        Once we found a problem, we added a new field to the form using DBSUM. TOTAL occasionally returned the WRONG number, and when it did, this number seemed to "stick" to other records. However, DBSUM always returned the correct number.
        There can be only one.

        Comment


          #5
          RE: Calculation problems

          Syntax:

          Sum Of Values = DBSUM(LookupTable, IndexTagName, KeyValue,
          LookupExpression)

          What could I put in the KeyValue to represent the ID# that is currently on the screen?

          Comment


            #6
            RE: Calculation problems

            If ID# is the field name, you use ID#, which refers to the value of that field in the current record. Note that you must have an index tag on ID# as well.

            The documentation is not clear on this as it gives only examples of using a stated value in the "Keyvalue" portion of the expression. Just drop in any indexed field name and it's index tag name.
            There can be only one.

            Comment


              #7
              RE: Calculation problems

              An additional note:

              The online documentation gives the example

              DBSUM("ORDER.DBF", "CUST_ID.MDX", "C102", "AMOUNT") with all of the parameters in quotes.

              If you use a field name in place of the "keyvalue" - !!! do not put it in quotes !!! Alpha will think you are looking for a keyvalue equal to the text string of your field name. Without the quotes, Alpha evaluates the field name's "contents".

              So in the above example, to find the sum of the amount field for records in the order.dbf, with an index tag of cust_id, with the keyvalue of the cust_id of the current record, the expression is:

              DBSUM("ORDER.DBF", "CUST_ID.MDX", cust_id, "AMOUNT")
              There can be only one.

              Comment


                #8
                RE: Calculation problems

                Thank you Stan for that additional note it did save me from killing something.

                It is doing one peculiar thing...

                When a master record has no child records, it gives a number that seems to be a sum of all master records instead of 0

                Comment


                  #9
                  RE: Calculation problems

                  I have no idea if this will work, but try changing your calculated field to catch the empty child field records.

                  Maybe

                  if(isblank("childfieldname"),0,yourdbsumexpression)

                  or as from the example before:

                  if(isblank("cust_id"),0,DBSUM("ORDER.DBF", "CUST_ID.MDX", cust_id, "AMOUNT"))

                  Keep the quotes around the field name in the isblank().
                  There can be only one.

                  Comment


                    #10
                    RE: Calculation problems

                    That did the trick thanks very much for your help

                    Comment

                    Working...
                    X