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
Devcon 2020 Goes Virtual! LEARN MORE >

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

tablesum()

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    tablesum()

    I know there has quite a few posts on this subject but I just can't get it to work. I have a INVOICE_HEADER table with a 1:M link to INVOICE_ITEMS child table, with the linking field being Inv_No. I want the field "subtotal" which is in the INVOICE_HEADER table to show the total for the field "ext" from the INVOICE_ITEMS table, I've read the help files and tried it so many ways I'm make myself more confused. Can someone please post an example using my fields?

    -Stan, I know you have answered me before on this, but I'm still stuck, Thanks

    Frank
    Tags: None
    #2
    Re: tablesum()

    Originally posted by Frank Calandro View Post
    I know there has quite a few posts on this subject but I just can't get it to work. I have a INVOICE_HEADER table with a 1:M link to INVOICE_ITEMS child table, with the linking field being Inv_No. I want the field "subtotal" which is in the INVOICE_HEADER table to show the total for the field "ext" from the INVOICE_ITEMS table, I've read the help files and tried it so many ways I'm make myself more confused. Can someone please post an example using my fields?

    -Stan, I know you have answered me before on this, but I'm still stuck, Thanks

    Frank
    If you make subtotal a calculated field in the invoice_header table with the expression

    Code:
    TABLESUM("invoice_items","invoice_number = "+QUOTE(INVOICE_NUMBER),"ext")
    (assumes invoice_number is a character field in both tables)

    and re-evaluate the field rules you will have what you want. The issue will be that adding items to an invoice will not change the first calculated value because nothiing in the record will trigger it. A similar record event field rule for the cansaverecord event would have the same issue. When you add a record to the invoice items table, nothing changes in the invoice header table to trigger the event.

    I suppose you need a posting field rule from the invoice items table to the invoice header table. Sorry I don't have much experience there.

    This all begets the question. Why do you want to store the subtotal in the invoice header table? I would think that having that info visible on a form or report would be sufficient. Displayed in this manner, the calculation would be performed when the layout is shown and the calculation would be current.
    There can be only one.

    Comment

      #3
      Re: tablesum()

      I've tried posting from the "ext" field in the INVOICE_ITEMS table to the INVOICE_HEADER table, and that works fine. The problem is when for some reason the item gets put on hold, unless I go into the form and manually type "0" in the qnty field, it does not back it out. If I use the set field value function and set it to "0", it doesn't have the same effect as if I actually type it. Putting the condition "backordered=.F." on works if backordered is checked before the record is saved the first time.

      I wanted to post to the INVOICE_HEADER table so it is easier to keep track of A/R. Many of my customers make partial payments, and I thought this might be a fast way to keep track of it. I'm very new at all this, so I'm sure there is a better/faster/more efficient way, but I havn't found it yet.

      Comment

        #4
        Re: tablesum()

        Originally posted by Frank Calandro View Post
        I wanted to post to the INVOICE_HEADER table so it is easier to keep track of A/R. Many of my customers make partial payments, and I thought this might be a fast way to keep track of it.
        I don't know how you keep track of A/R but I would imagine that you print a report or view a customer's invoice information on a form? If you make a calculated field for either, the subtotal will be current as of the moment the layout is generated. No posting, no field rules, no hassle.

        Suppose you work from a form. Via that form you locate an invoice. On the form the object name of the invoice_number field is invoice_number. The expression for a calculated field for the form would be

        Code:
        TABLESUM("invoice_items","invoice_number = "+QUOTE(INVOICE_NUMBER.value),"ext")
        INVOICE_NUMBER.value reffering to the contents of the visible field object. The subtotal field would be generated/recalculated each time you move from invoice to invoice and each time the form is opened.
        There can be only one.

        Comment

          #5
          Re: tablesum()

          What is your suggestion for the best way to keep track of accounts receivable with multiple payments. I was trying to post the total to another table with cust Id, invoice num, balance, payment type, type, etc. and make new forms off of that, keeping track of the payments from there.

          Frank

          Comment

          Previous template Next
          Working...
          X