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

On_save trigger?

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

  • On_save trigger?

    On my invoice form that I'm building, the line items' discounts will be automatically calculated based on about 30 parameters using customer discount tiers and wholesale discounts, way too long and diverse to put into an "if" or "case" statement in field rules. My web site does this by using xbasic code. If I were to copy that code, I would put it into a "save record" event, but unlike Alpha Four(!!), there's no "on_save" trigger that I can find. And how do I make it pertain to the discount field since there's no t=table_open() and t.discount variable that can be used (is there?). There's an event designer for the field I could use, but it seems that the field has to be entered to fire the event. What's the way to do this so it writes to the field when it's never touched? Oh, yes... then the discount just written has to be multiplied with the quantity and price to populate the "extended" field. Or do I do that with xbasic also?

  • #2
    Re: On_save trigger?

    there's no "on_save" trigger that I can find.
    There is the onsave event for forms. (Object events)

    There is the onsaverecord event for use in field rules. (Field rule events)
    There can be only one.

    Comment


    • #3
      Re: On_save trigger?

      there's no t=table_open() and t.discount variable that can be used (is there?).
      You can obtain a pointer to a table in use by the form with

      t = table.current([n])

      and then reference that table's fields with t.fieldname.

      You might investigate the cansave form event instead of the onsave. This allows you to make changes before the record is actually saved and is still in change mode. One less detail to deal with.
      There can be only one.

      Comment


      • #4
        Re: On_save trigger?

        Thanks for your responses, Stan. You're really helping me. Further on this subject:

        But then should the script also calculate the "extend" field before the save too, or will the calculated field rule for "extend" do this? Personally, I'd like the entire sequence to be in xbasic, but I'm afraid that this would override something that shouldn't be.

        Comment


        • #5
          Re: On_save trigger?

          I would do the computation in the xbasic and post it with the xbasic to a non calculated field rule field. That's a preference, not a should.
          There can be only one.

          Comment


          • #6
            Re: On_save trigger?

            Originally posted by Stan Mathews View Post
            You can obtain a pointer to a table in use by the form with

            t = table.current([n])

            and then reference that table's fields with t.fieldname.

            You might investigate the cansave form event instead of the onsave. This allows you to make changes before the record is actually saved and is still in change mode. One less detail to deal with.
            If you use the table's CanSave or OnSave Record event, there is no need to use [n] because table.current() will ALWAYS refer to the table that the CanSave or OnSave event is associated with. (Makes perfect sense if you think about it.)

            This is one reason why I always consider the Can/OnSave RECORD events as primary. The other reason is because I'm lazy - normally any Can/OnSave event should apply to any record no matter what form is being used. (If not, I would think long and hard about what might be wrong with my logic.) In that case, why would I want to duplicate the event on each form? Not only does it take more time, it's prone to more mistakes and it's highly likely to cause a problem later if I edit the script and forget to do it on one or more of the forms.

            Here's another thought. If you use the CanSave event in two forms based on different sets where the table in question is at a different level in each set, then you have to worry about setting [n] correctly - even when editing. And, if you edit the set it's possible to change the value of [n] - not common but it does happen. Now you have a real mess on your hands getting that [n] correct in every case. If you use the table event, the [n] doesn't even exist so it's not a concern - do it once and forget it.

            Comment


            • #7
              Re: On_save trigger?

              I used the canSave event, entered my very long code and voila! it works like a charm. Thanks for your help, guys!

              Comment


              • #8
                Re: On_save trigger?

                normally any Can/OnSave event should apply to any record no matter what form is being used
                Unless you are using the event to capture a form specific calculated field value to the table field. In that event you would have to code the table cansaverecord event to see if the form is open and not execute the code if it isn't.
                There can be only one.

                Comment

                Working...
                X