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



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

retaining calculated fields on record update

  • Filter
  • Time
  • Show
Clear All
new posts

  • retaining calculated fields on record update

    I have a field in "table a" named "disc"
    It holds a calculated value based on
    "LOOKUPN("F", CLIENT_ID, "discount_rate","clients","client_id")
    No problems there but the "discount_rate" in the "clients" table can be changed from time to time.
    There are multipe records in "table a" holding the "disc" value.
    Can the original "disc" field value in each record be maintained when a record is updated?

    Any help most welcome.

  • #2
    Re: retaining calculated fields on record update

    Originally posted by johnG View Post
    I have a field in "table a" named "disc"
    It holds a calculated value based on
    "LOOKUPN("F", CLIENT_ID, "discount_rate","clients","client_id")
    No problems there but the "discount_rate" in the "clients" table can be changed from time to time.
    There are multipe records in "table a" holding the "disc" value.
    Can the original "disc" field value in each record be maintained when a record is updated?

    Any help most welcome.
    change from the calculated value to a default value and put a skip rule
    on the field. Or, you could put the expression result on the form (if the rule
    does NOT apply to all forms for the table)


    • #3
      Re: retaining calculated fields on record update

      JohnG, no. If you continue to use the calc field rule it will re-evaluate the field value each time a record is saved. A user entered update to an existing record (after a change in the discount rate in the lookup table) would cause the previous calc field value to change. I think this may be inferred from John L's reply, but wanted to go ahead and spell it out for you.


      • #4
        Re: retaining calculated fields on record update

        Tom / JohnL thanks for the replies... as the entry wasn't entered via a form but a script I have changed the field rule to 'user entered' and then added code to the script which seems to work just fine. Just got to change some more codes in simialr scripts and all should be well
        Many thanks


        • #5
          Re: retaining calculated fields on record update

          Since, based on the number of posts, it appears that you're relatively new to A5, you might want to check out this thread about setting "last changed" dates. (Hint - they should NOT be calculated fields!)

          FWIW: Almost every table I build has a Create_dtf and Change_dtf. Even if it isn't "needed", I often find out that it really is needed! There have been a number of times in the past when someone has come up with a request that would be easy to do if I just knew when the records were created/changed but, since those dates weren't "needed" they weren't available. I've also had people tell me that there was no way the record was changed since X months ago - then I show them the Change_dtf that says it was changed yesterday and all of a sudden the story changes. These dates are often not shown on any forms; they are just 'there' in the table in case I need them.

          It may seem stupid to some but almost every table I build now, even a simple lookup table with one "real" field, will include those two date fields. Having them there has either enabled me to do something that wouldn't have been possible otherwise or saved me from major problems a number of times.