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

FIFO Inventory / Storage Fee Accrual problem...

  • Filter
  • Time
  • Show
Clear All
new posts

  • FIFO Inventory / Storage Fee Accrual problem...

    I'm working with Alpha 5 version 4.5 build 266.

    I'm working on a database that records prolonged storage of large quantities of beans. Farmers will drop off batches of beans over a period of months. After a 30-day grace period, storage fees are calculated daily.

    Scenario: Let's say a grower dropped off 50,000 lbs of beans, and then another 50,000 lbs a month later. Three months later, we sell 70,000 lbs.

    When we make the sale, my form needs to show how much total accrued storage fee we should charge for the 70,000 lbs.

    I have field rules set up that automatically calculate number of days in storage for each batch of beans, but how do I set it up so that the sale subtracts from the oldest batch of beans first and then subtracts the rest from the next recent batch?

  • #2
    RE: FIFO Inventory / Storage Fee Accrual problem..


    Don't laugh but the medical people are going to help you on this one because they have had to solve the problem of applying a payment to multiple invoices starting with the oldest one and moving forward in time.

    It was Peter Wayne and Ohlen Cartmell if I remember right and the post will be on the Version 4 board--this board.

    Seems to me you will have to order deliveries by date, starting with the oldest:
    -subtract a sale amount from the first invoice
    -calculate storage days
    -remember any remainder so you can carry it over to the next delivery

    -repeat the process.

    I know I have left a lot out.

    Search the board for "apply payments to multiple invoices". It will get you started.

    Bill Hanigsberg


    • #3
      RE: FIFO Inventory / Storage Fee Accrual problem..

      Thanks William :-)

      I found the article at

      I'm still a novice at code, but from the article, it looks like my first step is to dig into setting up code for a query that'll put my dates in a sequence that Alpha can use.

      If I figure this out, I'll post an example of the code.

      Thanks for the tip. :-)


      • #4
        RE: FIFO Inventory / Storage Fee Accrual problem..


        A good way to get started with script writing is to build a system that does what you want manually.

        For instance, in your case, you could add a field to each receiving transaction record to display the remaining portion of the original transaction which still remains in storage.

        When a sale occurs you could display the receiving transaction records in a browse object, and manually allocate the sale among the oldest entries. Doing this several times will help you understand the sequence your script must follow to automate the allocation process.

        -- tom


        • #5
          RE: FIFO Inventory / Storage Fee Accrual problem..

          Thanks for the feedback Tom :-)

          The possibility of setting up a manual entry form next to a browse that shows remaining balances of each batch had occurred to me, and I've been leaning towards doing that until I can figure out how to get Alpha to do it automatically. I can understand the sequence of events and logic that Alpha must follow, but frankly, I'm stumped about the Xbasic code for it.

          I just now getting to the "Queries?" chapter in "Alpha Five: Xbasic for Everyone". If I make any headway, I'll be sure to post.