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

Are grid components the answer?

  • Filter
  • Time
  • Show
Clear All
new posts

  • Are grid components the answer?

    As a new user to A5, I need to write a routine for applying payments to specific invoices. The number of invoices being paid with any 1 payment could be anywhere from 1 invoice to 130 invoices. Having read the message board, I know there are some of you that disagree with this approach. That being said, I still come here looking for guidance and direction on the best way to precede. I am looking to be able to mark the specific invoices that are being paid and keeping a running total of marked invoices. I want to be able to block the user from saving the transaction if the payment has not been applied in full. Also I would like to be able to toggle back and forth between a list of full amounts and a list of discounted amounts. The invoices would normally be listed in chronological order. Would it be possible to reorder the list by ascending order of the invoice numbers? From the reading that I have done, everything seems to point to a grid component as the only way to go. However, according to Selwyn Rabins, "If you have the skills, putting a Grid component on a form has been available since v10 came out because you could embed the Grid in an xdialog and then embed the Xdialog into a form. However, the skill level required for this is high." I do not consider my skill level to be high. If this is in fact the route I need to take, where is the best place for me to learn about grid components? Any and all suggestions on the direction I should take would be greatly appreciated. Thanks in advance.

  • #2
    Re: Are grid components the answer?

    I do this without using a grid component.

    Others may have a simpler or more efficient approach, but here's how I do it.

    I keep the unpaid balance for each invoice in the invoice header.

    I use a two table set to track payments. The header stores details like payor, check amount, chk date, chk number etc The child table I call pay_splits. Each record is populated using a filtered table lookup field rule so the user can pick each invoice being paid. The split payment amt in each of the child records defaults to the invoice unpaid balance, but it can be changed by the user to accommodate partial payments.

    As pay_splits are entered a running total is used to compare the sum of all the splits with the check amount.

    When the entire check has been allocated the user pushes a button and scripts run which apply the splits to the unpaid balance figures in each of the invoices, otherwise the payment header and all the splits are deleted.

    I think of the payment set as a sort of scratch pad collecting information on how the payment should be applied. Only after its in balance and the user accepts the allocations, are the original invoice balances changed.

    My system works well if the operator is careful. However, making edits or changes after committing the initial pay splits is a messy business that I haven't smoothed out just yet.