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

summary function on new records in a grid

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

    summary function on new records in a grid

    In an application similar to an Accounts Receivable payment process I would like to be able to accomplish the following:
    Record the total amount of the payment and disburse it to the proper invoices, while keeping track of the amount applied to each invoice and the unappliedamount remaining.

    The payment itself would be a separate table, and the payments applied to each invoices would be records in a different table.
    I do not want to commit the grid until the entire payment has been disbursed completely, and not overapplied nor underapplied.

    I tried using the total summary function in a grid, but that will not keep track of the total unless the records are committed (unless I am missing something).
    I believe the essence of the problems is trying to total the applied payments before the record is actually saved.

    I cannot think how to resolve this using javascript, nor an ajax callback, as the grid will not be submitted until the payments are disbursed completely.

    Any thoughts?

    Thanks,
    Jay
    Jay Talbott
    Lexington, KY


    #2
    Re: summary function on new records in a grid

    Jay, tell me if this is an accurate understanding of what you are trying to do:

    Customer pays $100.00.
    Customer has bills for the following three invoices (totaling $110.00):
    101 -- $50.00 for bowling ball
    102 -- $35.00 for shoes
    103 -- $25.00 for bag

    You then want to apply:

    $50.00 to inv. 101 (full payment)
    $30.00 to inv. 102 (partial payment)
    $20.00 to inv. 103 (partial payment)

    You want to be able to apply varying amounts to each inv., but make sure the entire payment is used (though not necessarily paying each invoice in full). You do not want to commit anything until you have allocated all of the payment.

    If this is the case, let me know. I have an idea of how to tackle it, but don't want to put time into it if I'm off the mark here.
    Stephen Pilon
    Associate Librarian
    Christendom College

    Comment


      #3
      Re: summary function on new records in a grid

      Stephen,
      You are correct. That is what I want to do.
      Of course, one customer might have 2 invoices, another 1 invoice, and another 6 invoices.
      But your construct is correct.
      Thanks,
      Jay
      Jay Talbott
      Lexington, KY

      Comment


        #4
        Re: summary function on new records in a grid

        Jay, I have two snippets of code for you to try. First, use this in a free form area of the grid:

        Code:
        <select id="list1">
        	<option>1</option>
        	<option>2</option>
        	<option>3</option>
        </select>
        <input id="text1" type="text"></input>
        <button id="button1">Apply</button>&nbsp;&nbsp;
        <a href="#" onclick="a5_AJAX_Callback('misc.ajax.a5w','action=addrow&whatrow=2');">add row</a>
        <br />
        <span id="newrow2"></span>
        Then put this is a new a5w page called misc.ajax.a5w:

        Code:
        <%a5
        if eval_valid("action") then
        select
            case action = "addrow"
        		dim whatrow as c = default "0"
        		if whatrow > "1" then
        			dim rowhtml as c
        			rowhtml = "<select id=\"list"+whatrow+"\"><option>1</option><option>2</option><option>3</option></select> <input id=\"text"+whatrow+"\" type=\"text\"></input> <button id=\"button"+whatrow+"\">Apply</button>&nbsp;&nbsp;<a href=\"#\" onclick=\"a5_AJAX_Callback('misc.ajax.a5w','action=addrow&whatrow="+ut(str(val(whatrow)+1))+"');\">add row</a><br /><span id=\"newrow"+ut(str(val(whatrow)+1))+"\"></span>"
        			? "$('newrow"+whatrow+"').innerHTML = '" + js_escape(rowhtml) + "';"
        		end if
        end select
        end if
        %>
        Publish both and press the add row button. This adds any number of rows. Then use a similar construct to populate the fields in the rows that are being returned via the callback. Since the callback takes place in an xbasic block, you have full access to tables, etc.

        In order to know what values have already been used, include something like this in the callback:

        Code:
        a5_AJAX_Callback('action=addrow&whatrow=2&prevlist='+urlencode($('list1').innerHTML)+'&prevtext='+urlencode($('text1').innerHTML));
        I know I don't have all the pieces worked out, but hopefully it provides a starting point.

        Another (non-ajax) option might be to use two tables called Payments and Allocations.

        Payments would simply track the payment itself:
        • Payment_Id
        • Payment_Amount
        • Payment_Remaining (initially same as Payment_Amount)
        • Customer_Id
        • Salesman_Id
        • Payment_Type
        • Payment_Date


        Allocations would track payment disbursement:
        • Allocation_Id
        • Payment_Id
        • Invoice_Number
        • Allocation_Amount


        You could use a Post field rule to update the Payment_Remaining with each allocation entry. Although this does not accomplish waiting to commit until all disbursements are made, it seems like a valid method, since you can work them back and forth and the post rule will keep the Amount_Remaining up-to-date.

        I hope one of these ideas works.
        Stephen Pilon
        Associate Librarian
        Christendom College

        Comment


          #5
          Re: summary function on new records in a grid

          Thank you Stephen, I will give it a try.
          Jay
          Jay Talbott
          Lexington, KY

          Comment

          Working...
          X