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

Cash receipts / payments routine guidance

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

    Cash receipts / payments routine guidance

    How can I create the following cash receipts / payments form... (Question has been in my mind since 2006...)

    I'm just looking for proper methodology, not a full solution here.

    FORM / TABLE SETS / REQUIREMENTS:
    While creating a cash receipts / payments routine, the form/layout must do the following:

    1.) NEW PAYMENT SCENARIO:
    Build a form / subform displaying all unpaid invoices for customer to display in sub form.
    (individual amounts can be assigned to each unpaid invoice.

    Within this form, the underlying query (or table set) must:
    -be retrievable in the event user wishes to edit an existing payment. (see UPDATE PAYMENT SCENARIO below)
    -include one extra field to record payment amount applied to individual invoices.
    -show a sum of all previous payments applied to each specific invoice. (one invoice on each line of subform.)

    Upon re-edit of a previously entered payment, this extra field must also populate with the prevous entered payment amounts (which could be $0), and then be editable for change. (Again, see UPDATE PAYMENT SCENARIO as follows.)

    2.) UPDATE PAYMENT SCENARIO:
    Use the same form/layout, but now show previously entered applied payments via transaction lookup:
    -Form must be able to retrieve existing (previous) transactions, and show by line item how payment was applied to individual invoices.


    THE FOLLOWING IS ABOUT AS FAR AS I EVER GET IN MY THINKING PROCESS:

    SQL / table / sets scenario:
    customers have many invoices. (1 - ~)
    invoices can have many separately applied payments. (1 - ~)
    And each payment transaction therefore can have many line items (aka invoices.) (1 - ~)
    (but can also have 0, since it is possible to make an advance payment where no invoice yet exists.)


    POSSIBLE APPROACH #1: (using summary table)

    Because I want to display one line item for each outstanding (unpaid) transaction...

    First create a new "temporary" summary table based on existing payments for customer.
    -This table (table T) is generated every time a new payment is made. (becomes part of the subform / details data)
    -This table shows the totals paid to date summed by invoice / purchase transaction.
    -The payments details (subform) is then based on a set as follows:
    summary (temporary table T) table is linked (the many side) to the payment transaction detail table (table P).

    Regardless, the problem I keep postulating under this approach is as follows:

    The above scenario would presumably work when pulling up existing payments for re-edit.
    But when appying new payments, I can't figure out how to display (on the subform) one line for each unpaid

    invoice, because table P (on the one side of the one to many set relationship) has no itmes to display. (until

    the new transaction is actually saved.)


    POSSIBLE APPROACH #2: (subform based on different data)

    Then I begin to wonder if I need to create a form which has a subform based on different sets depending on whether user is entering a new payment, or editing a previous payment.

    Under this scenario, my logic is as follows:

    For new payments...
    -Make the subform use a crosstab query for data, and then append this data to a payments detail table.

    And while editing/deleting payments...
    -Make the subform display existing payment data. (in much the same way as a simple invoice pulls up details)
    -This would solve all the editing problems, including deleting the entire transaction. (A delete could either set
    a flag so this transaction info is not included in the crosstab query above (when making new payments), or a
    delete records function could be used.

    Here the problems I encounter is:

    How do I create a form with a subform based on a set which is dynamically assigned from within the header. Maybe

    one solution here is to have a "NEW" button which loads an alternate form. But this seems like cheating.


    POSSIBLE APPROACH #3: (table set linking back to itself)

    Create a table set, somehow linked back to itself. (Using include all even if no matching child exists.)
    Then I could append this table back into the payments table and use some of the methods previously mentioned above.

    But here, how can I display the sum of all previously entered payments for each line item?


    FINAL IDEA:

    **With version 9, I'm also wondering if this a scenario which can be somehow greatly simplified by using the new "mapped tables" feature...


    Maybe this is just a exercise for a SQL guru, I don't know.

    Any insight here on the correct / viable / preferred way to do this will be greatly appreciated....

    AAAaaaarrrrrrgggggg.....
    Last edited by SNusa; 02-24-2009, 11:56 AM.
    Robert T. ~ "I enjoy manipulating data... just not my data."
    It's all about the "framework." (I suppose an "a5-induced" hard drive crash is now in order?)
    RELOADED: My current posting activity here merely represents a "Momentary Lapse Of Reason."

    #2
    Re: Cash receipts / payments routine guidance

    Almost forgot......

    Insight on the best way to do it using A5 native tables is a good start and would be very helpful.
    Could field rule posting be part of the solution here????

    BUT ULTIMATELY, I want to build this off a MS SQL (2005) back-end using the Alpha ADO connection type for maximum functionality.

    Presumably, using field rule posting events may even work here too. (when using the SQL Alpha ADO connection.)
    -Back with version 8 that wasn't possible. (passive links only - basically no writing to MS SQL)

    RELATED QUESTIONS:
    1.) Are a5 SETS (created from actively linked SQL TABLES) even update-able in the first place?
    2.) *Under what conditions (if possible) are a5 active link TABLES and/or SETS (based on SQL QUERIES) editable?

    *I ask this (question #2) because all the examples I have seen in the training info (from Alphasoftware) show linked sql based tables (including the active linked ones in a5) as not being editable. Mabe only TABLES linked from sql can be editable?
    Last edited by SNusa; 02-24-2009, 01:50 PM.
    Robert T. ~ "I enjoy manipulating data... just not my data."
    It's all about the "framework." (I suppose an "a5-induced" hard drive crash is now in order?)
    RELOADED: My current posting activity here merely represents a "Momentary Lapse Of Reason."

    Comment


      #3
      Re: Cash receipts / payments routine guidance

      OOPS.... Been thinking in a5 terminology too much....

      When I was referring to sql QUERIES in above post, I meant sql VIEWS!

      Sorry...
      Robert T. ~ "I enjoy manipulating data... just not my data."
      It's all about the "framework." (I suppose an "a5-induced" hard drive crash is now in order?)
      RELOADED: My current posting activity here merely represents a "Momentary Lapse Of Reason."

      Comment

      Working...
      X