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

saving a forms calculated field

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

    saving a forms calculated field

    I have a calculated field on a form that I want to save to a corresponding field in which the table is based. Basically, I am computing sub-total, discount, tax etc. on a form and have fields in the table for the same. I have seen before where a value can be transferred in this situation.

    Any hints are appreciated.

    Alex Levy
    Alex Levy
    Tampa, FL

    #2
    RE: saving a forms calculated field

    Alex,

    Context is everything.

    /begin hint

    If the table(s) that you need to update are the same as the table(s) upon which the current form is based, they're already open. Otherwise your script will need to open them.

    Once a destination table is open you must determine whether the correct record is 'current', assuming the record is already present in the table. Otherwise, you would want to begin entering a new record, right? If you are working with the tables that support your form what you see on screen should tell you which record is 'current'. If the record pointer in the destination table is not positioned at the desired record, your script would make an index primary, and then do a fetch_find to position the table to the desired record, thereby making the desired record current.

    next your script must determine whether the table is in change mode already, or can be placed in change mode. The goal is to put it in change mode so you can write values from your form into the current record.

    Then your script should assign the calculated value(s) to each field. you can batch fields in the same record if you wish. Then, depending on what you want, you can leave the table in change mode, so that other input might be received, or, more commonly, you'd commit the changes to the table.

    If you need to update fields in more than one table you must repeat the same sequence for each of them.


    /end hint

    Comment


      #3
      RE: saving a forms calculated field

      Evrything is done and works ok about synchronizing the record with the current record. I guess what I am trying to figure out is how to "assign" a value of a calculated memory variable to a field ?
      Alex Levy
      Tampa, FL

      Comment


        #4
        RE: saving a forms calculated field

        Alex,

        The discussion in the xbasic reference manual on

        tbl.change_begin()

        will help. The second example illustrates how simple character strings can be assigned to a field. In your case you don't want to assign a literal string of characters, so you wouldn't use quote marks. Instead of surrounding the string with quote marks, just use your variable's name (without quote marks of course).

        -- tom

        Comment


          #5
          RE: saving a forms calculated field

          Since you want to save these values, why not make them field rule calculated fields? Then they'll always be a part of the table and the current record.

          Comment


            #6
            RE: saving a forms calculated field

            Yes, that is what I could not remember. Program is updated and working correctly.

            Thanks

            Alex
            Alex Levy
            Tampa, FL

            Comment

            Working...
            X