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

AR - Multiple Checks from same Cust

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

    AR - Multiple Checks from same Cust

    I have created an AR payment module, that goes over and grabs all outstanding receivables and copies to a "temp" payment folder. Then I made a set that is ARChecksTemp - Temppymts. When you enter a check header for a customer, all receivables for that customer number then show in the browse on the form and by selecting "YES" on the receivables line it marks for payment and marks it with the check date, method type and reference #. Then when all checks are entered - POSTING sends the receivable payments "marked" to a permanant folder for payments, posts a copy of the check total to the AR Checks table, and posts the amounts to the actual receivables and clears them. All this works great, except I now have a client that will get several checks from one customer in a single deposit. Because the set is linked by "Cust#" multiple check headers can't be created for a single customer. There are also times when one customer sends one check to pay on several different accounts.

    Anyone built a module that allows for several checks from a single customer in one deposit or the ability to split a check to several accounts. If so, would you mind pointing me in the direction you went to accomodate this need.

    Thanks again, Lynda




    #2
    RE: AR - Multiple Checks from same Cust

    one check to pay several account, you could do this:

    build a form that you can enter cust#:
    1) search for cust# in invoices,
    2) loop through the invoices, if check amount " one invoice amount, put the invoice amount in invoice payment,
    check_amount=check_amount- invoice amount
    3) loop through 2 until the check amount = 0
    :) Romy

    Comment


      #3
      RE: AR - Multiple Checks from same Cust

      In my invoice application, I put three check number(max), amount, payment date.
      :) Romy

      Comment


        #4
        RE: AR - Multiple Checks from same Cust

        Are you saying in the ChecksTemp Header, put three check ref, amount fields?

        How would you then flag each line item to a check. In the set the outstanding receivables have a "Full" pymt field, or a manually entered amount field. When selecting "YES" under Full or typing in an amount, the field rules then recalculate (ref # does a lookupc(checkheader,custno,custno,reference) and fills in the above check ref #, same with method and date....

        Then when it posts to a permanant payment log, I can see what items each check has paid (now hooked by ref#).

        If I have three fields in the check header for three check entries - how does the item know which one to fill in on the line item?
        Thanks again for the help...
        Lynda

        Comment


          #5
          RE: AR - Multiple Checks from same Cust

          I have a application invoice. One invoice(for one cust#) has several line items, and total amount for total items. Put three check ref#s in one invoice. You can manual enter in the check ref# and amount in the invoice form.
          2) automatically enter: you can create a form ask user to enter cust#, have several check ref#s, amount #s and a button. On the button push event, you can look for the invoices for the cust#, put check ref# and amount to three check ref#. and amount of invoice table.

          For example:
          Customer #234 pay four check #1 $100.00, #2 $200.00, #3 $300.00, #4 $400.00.

          1) search for Customer#234.
          2) found 3 invoice:
          a) #1 340.98
          b) #2 456.34
          c) #3 435.89
          3) put check ref#1 to inv#1's check_1, 240.98 left. put ref#2 to inv#1 check_2, put ref#3 to inv#1 check_3. ref#3 still has $259.02, put to inv#2... until total check was filled.
          :) Romy

          Comment


            #6
            Re: AR - Multiple Checks from same Cust

            Lynda,

            I have structured a separate set for accomplishing the same task. As starters, an invoicing routine automatically posts to a separate table "customer sales", the basic components of a sales table contains the fields (( cust id; invc #; invc date; invc amount; paid,yes or no )). Assume the paid yes or no field is a character field of 1
            and "P" = paid and "U" = unpaid. All new entries invoiced are automatically marked as "U".


            I have a regular set "ac receiv" linking customers to customer sales by Customer ID


            Another set links customers to deposits by customer id; deposits to customer sales
            by check number and customers to sales by customer id, using the filter "paid yes or no = "U"


            At the top of the screen is whatever customer data you need to display. I keep it vey basic.
            The table displays on the left all deposits from a single customer. The table on the right is all of the invoices paid with a single check. As you scroll down the deposit table, the specific invoices paid by that check are displayed. Logical calc fields display the total of invoices paid and should equal the check amount. A separate logical field displays zero if they match or any difference if they do not.

            In this same set, I have linked customer sales as a third table using the filter "U"

            This table lists all unpaid customer invoices.

            If you post a new customer check payment in the deposit table, you can then mark the invoices in the unpaid customer sales table on the bottom. Logical calc fields can summarize the amount being posted and should equal the amount of the check when done. You can also convert the "U" to "P" at the end of the postings.

            Will this arrangement help,

            John Linley
            Last edited by john linley; 07-23-2008, 06:41 AM. Reason: wrong word

            Comment

            Working...
            X