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

Placing a Calculated Field Result in Another Field

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

    Placing a Calculated Field Result in Another Field

    I know calculated fields are not a true field in the sense that they are completed "on the fly". I have been trying to find a way to place the result of a calculated field in another field in the same table without success. Is there a way to update a field with the result from a calculated field? Thanks for any and all replies.

    Scott

    #2
    Re: Placing a Calculated Field Result in Another Field

    CanSaveRecord field rule event script.

    tbl =table.current()
    tbl.destination_field_name = tbl.calculated_field_name

    Not sure what that accomplishes other than storing the same data in two places.
    There can be only one.

    Comment


      #3
      Re: Placing a Calculated Field Result in Another Field

      Probably for after the form has closed

      Retraction after reading again:
      the original question says "in the same table" - yes why?

      Comment


        #4
        Re: Placing a Calculated Field Result in Another Field

        The info will be stored in 2 fields in the same table. Yes it sounds redundant. The problem I'm having is the result in the calculated field cannot be exported. I need to be able to export the result. I figured that by utilizing a field the customer cannot see I can then export the result as it will then actually be stored in a true field that exists in the table. Thanks for the replies guys it helps tons.

        Comment


          #5
          Re: Placing a Calculated Field Result in Another Field

          The problem I'm having is the result in the calculated field cannot be exported.
          Just tried it, still works.

          Calculated fields defined for a layout cannot be exported, calculated fields for a table are real fields like any other and can be exported.
          There can be only one.

          Comment


            #6
            Re: Placing a Calculated Field Result in Another Field

            THanks Stan I was not aware of that. The calculated field I'm currently using is for the layout and not an actual calculated field in the table. Many thanks again.

            Comment


              #7
              Re: Placing a Calculated Field Result in Another Field

              Then my earlier advice is not valid.

              Best to put the storage field on the form and hide it.

              Then

              storage_field_objectname.value = layout_calculated_field_objectname.value
              There can be only one.

              Comment


                #8
                Re: Placing a Calculated Field Result in Another Field

                I just realized the problem I have with a calculated field in the table is that I'm using a custom function to fill in the info in the calculated field for the layout. The function pulls data from several different tables within the set to determine the correct data. If I use a field within my table then my function will not work as it won't see the other tables within the set. It should only see the fields within that table. Is this correct? If so, is it possible to take the result in the calculated field for the layout and place it in a field in the current table.

                Comment


                  #9
                  Re: Placing a Calculated Field Result in Another Field

                  I just saw your reply Stan. I'll try that .... thanks.

                  Comment


                    #10
                    Re: Placing a Calculated Field Result in Another Field

                    The suggested code is for the cansave event of the form. I erased that when composing/editing the reply.
                    There can be only one.

                    Comment


                      #11
                      Re: Placing a Calculated Field Result in Another Field

                      Hi Stan. I've tried your formula but I must be doing something wrong because nothing happens. The name of the field in the table is New_Price. The name of the calculated field for the layout is New. My code under the "CanSave" event for the layout is as follows:
                      New_Price.value=New.value
                      If I open a current record and unlock it, make a few changes then save it, I'm not getting the New_Price filled in at all. They're both set up as numerical fields. Should this perhaps be on the "OnSave" event? Not sure where I'm going wrong.....

                      Comment


                        #12
                        Re: Placing a Calculated Field Result in Another Field

                        The name of the field in the table is New_Price. The name of the calculated field for the layout is New.
                        Not pertinent.

                        You need the object name of the fields on the form. Right click on each, choose Properties, discover the object name.

                        OnSave happens after the record is saved when the table is no longer in edit mode.
                        There can be only one.

                        Comment


                          #13
                          Re: Placing a Calculated Field Result in Another Field

                          Just a necessary comment.
                          The precision required when addressing objects is vital to achieving what is required (as opposed to what you're thinking) - basics 101
                          Many posts went by here, even repeating precise wording of the question.
                          There is a major distinction between a form calculated field and a table calc field.
                          My point is, that careless description and lack of attention to the correct object (to save your time?) is wasteful of everyone else's time and effort. You wouldn't be programming in that manner or else you should be trying to.

                          Please people, if you want help, take the time and care to provide all information required and that it is described correctly - that's how you program right?
                          Last edited by Ray in Capetown; 02-21-2013, 02:47 AM.

                          Comment


                            #14
                            Re: Placing a Calculated Field Result in Another Field

                            This page and this page explains the difference between calc fields and calc values. Read it carefully, which in my case also means slowly.
                            Tim Kiebert
                            Eagle Creek Citrus
                            A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

                            Comment


                              #15
                              Re: Placing a Calculated Field Result in Another Field

                              Gentleman with all due respect and after double checking, the information I gave you is correct. Those ARE the object names and not just the field label. So, I'm still having the same problem. I double checked from the properties box and those are definitely the object names. I understand where you're coming from and I am not looking to needlessly take up[ anyone's time. Thanks for the replies.

                              Comment

                              Working...
                              X