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

Calculated Values

  • Filter
  • Time
  • Show
Clear All
new posts

  • Calculated Values


    I have the Calculate expression as following but some reason this ("xMtrTotal") is erased by A5 nor A5 does not keep this expression.
    xMtrSum = tablesum("change_itm","Change_Itm->Hdr_Id="+quote(Hdr_Id)+" .AND. Change_Itm->Costtype = 'Material' ","Change_Itm->Line_Sum")

    xStaxAmt = Round(calc->xMtrSum*calc->xStaxRate/100,2)
    xSTaxId = if(lookup("contracts","project_id="+quote(Project_Id),"Salestax_id")="excluded","",lookup("contracts","project_id="+quote(Project_Id),"Salestax_id"))
    xSTaxRate = lookup("salesTax","SalesTax_id="+quote(calc->Xstaxid),"State_tax_rate")

    xMtrTotal = calc->Xmtrsum + calc->xStaxAmt
    Does anyone advise me what is wrong in those expressions?

  • #2
    Re: Calculated Values

    You're nesting calc expressions inside calc expressions inside calc expressions. Alpha is deleting the last one because it can't resolve it. i.e. Alpha can't compute xMtrTotal until both Xmtrsum and xtaxAmt are first computed. Alpha can't compute xStaxAmt without first computing both xMtrSum and xStaxRate. xStraxRate can't be computed until xstaxid is computed. The result you need can only be achieved if the expressions are evaluated in the correct sequence. And, by the way, your list has them in the wrong order. Even re-arranging the sequence may be insufficient because some of these will be computed quickly, and others will take much longer. Yet, your approach assumes they'll all be available instantly. Sorry. It doesn't work like that.

    Suggest you write the expressions without nesting, or even better, write a udf. In my experience nesting calc fields like this is very difficult to maintain. They may make sense now, but in six months ... ?


    • #3
      Re: Calculated Values


      Thank you, I will try to write for an UDF but not sure how it works with a form.


      • #4
        Re: Calculated Values


        It is required more than my skill. I wrote some of the UDF and replaced the old Calculated Expression with UDF. Now, I still not able to use as simple like "Calc->abc + Calc->edf ". I think my form is simpler than AlphaSport Invoice except some of fields value(like a sales tax rate) is required to get from 3rd table and more Calculated value fields. The Calculated Expression took extremely hard to understand and fail and fail again.

        xLbrSum = Change_LbrSum(Hdr_Id)
        xMtrsum = Change_MtrSum(Hdr_Id)
        xOthSum = Change_OthSum(Hdr_Id)
        xOvHdId = lookup("contracts","project_id="+quote(Project_Id), "Overhead_id")
        xPrdAmt = calc->xStaxAmt + calc->xmtrsum

        xStaxAmt = calc->xmtrsum*calc->xstaxrate/100
        xStaxRate = salestax_rate()
        I have an warning as "Change_MtrSum = Tablesum("change_itm","hdr_id ="+quote(vhdrid)+" .and. ... 'Line_sum' not found " when the mouse over the "xStaxAmt" and the "xPrdAmt" expression is gone now.

        Tom, How can I avoid those errors in my case?
        Do I have to use the UDF in order to accomplish Sales tax calculation value?