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

Forcing calc fields to recalculate

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

    Forcing calc fields to recalculate

    Is there a way to do this via Xbasic?
    Gary S. Traub, Ph.D.


    #2
    RE: Forcing calc fields to recalculate

    gary:
    here is an old message that was on the board

    Charlie Crimmel

    If you change the value in another field on the form,
    you will see the new value in the calc field.
    But changing another field is not always desirable.

    Here's a script that will recalc the record you're viewing:

    t=table.current()
    t.change_begin()
    t.change_end(.t.)
    parentform.resynch()

    Note that you should NOT use HONOR_FIELD_RULES in the change_begin,
    because then it will NOT work! Also, the .t. forces the program to
    accept the change even though you haven't changed any values.

    Tom also had this script to re-evaluate a table:


    tbl = table.current()
    tbl.fetch_first()
    while .not. tbl.fetch_eof()
    tbl.change_begin()
    tbl.change_end(.t.)
    tbl.fetch_next()
    end while

    Comment


      #3
      RE: Forcing calc fields to recalculate

      Hi Charlie,

      Thanks for responding.

      I tried this method, and it does not work for me. I think the problem is that your method seems to require that the record be saved first, and that is not desireable in my situation. Are there any other ways to force a recalculation? Or am I misunderstanding what you mean?

      Thanks,

      Gary
      Gary S. Traub, Ph.D.

      Comment


        #4
        RE: Forcing calc fields to recalculate

        Gary,

        There are calc fields defined in the properties of a form.

        There are table fields whose values have been restricted to predefined expressions in field rules. These are call calc fields by custom.

        There are calc fields defined in the properties of a report.

        There are calc fields defined in the properties of a label layout.

        Asking about 'calc fields' is, unfortunately, not enough of a clue to tell us which kind you may be interested in.

        -- tom

        Comment


          #5
          RE: Forcing calc fields to recalculate

          Gary, you could also try objectname.refresh()

          but, the calculated field, if it is form/defined, would most likely have to reference form values as opposed to table values, as the record has not been saved yet, as the values are still in the buffer.

          like total.value=field1object.value + fieldobject2.value
          total.refresh() - should work, providing the two objects have a value
          Cole Custom Programming - Terrell, Texas
          972 524 8714
          [email protected]

          ____________________
          "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

          Comment


            #6
            RE: Forcing calc fields to recalculate

            Gary,
            I am not sure what type of calculations you are trying to do but I have calculated date fields on a form that update as soon as I enter a date, the calculated date field updates. I do not have to save the record and I can cancel the change. The calculation is set in the field rules for the calculated field.
            I hope this makes sense.
            Dick Blanchard

            Comment


              #7
              RE: Forcing calc fields to recalculate

              Presumably, it would probably be the form calc field. There is an issue there, as I have had problems too.
              Peter
              AlphaBase Solutions, LLC

              [email protected]
              https://www.alphabasesolutions.com


              Comment


                #8
                RE: Forcing calc fields to recalculate

                Thanks everyone for your comments. For a variety of reasons, I am using a table based calculated field.

                I a value is entered into another field on the form, the calculated field behaves as desired. However, I use a popup dialog form that lists several pre-defined transactions that the user can select, and when they do, all the fileds on the form are automatically field in by the popup. Works great, with the only exception being that the calculated field does not recompute, until either the record is saved, or the user manually changes a value in any of the fields.

                Gary
                Gary S. Traub, Ph.D.

                Comment


                  #9
                  RE: Forcing calc fields to recalculate

                  Take a look at http://support.alphasoftware.com/xbasic_reference/Methods/_TBL_.RECALC_CALCFIELDS().htm and http://support.alphasoftware.com/xbasic_reference/Functions/A5_RECALC_CALC_FIELDS().htm

                  Comment


                    #10
                    RE: Forcing calc fields to recalculate

                    Hi Ed,

                    Those seem like very useful functions, but I believe that they both operate on the table, and thus would not slve my problem because my calc field is on the form and the recalc needs to occur before the values are saved to the table.

                    However, building on the suggestion from Martin Cole above, I did come up with a work around. Rather than placing the table's calc field on the form, I defined a form based calc field and used the refresh() method to cause the calc field to update. This works fine.

                    Thanks again to everyone for your suggestions.

                    Gary
                    Gary S. Traub, Ph.D.

                    Comment


                      #11
                      RE: Forcing calc fields to recalculate

                      I have gone to both of these links and found the functions for recalc - it is what I needed. I have experienced problems, where you have a calculated field that takes total revenue spent on inventory and divides it by the total quantity in order to get average cost. However, when receiving updates both of these totals, it doesn't automatically update the calculated average cost field. So, my question is where is the best place to apply these functions. Do I place in an event in the inventory table, or do I make it part of a button event on the form? Any suggestions?

                      Here is the two codes I have found...
                      Tbl = table.open(�customers�)
                      Tbl.recalc_calcFields()
                      Tbl.Close()

                      A5_recalc_calc_fields(�Customer�)

                      Comment

                      Working...
                      X