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

Inventory

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

    Inventory

    I know I am making life difficult for myself but am totally confused and probably overthinking things. I want to create a browse that shows current stock levels of on-hand and what has been ordered received and not used. Is the best way to do this to have one table that keeps track of inventory additions and subtractions or to have two tables with one showing ordered material and one showing material usage and then creating a set?

    Help?!?

    Josh

    #2
    Re: Inventory

    The AlphaSports sample is not complete in this regard but the thought seems to be

    a products table which has current inventory
    an invoice detail table which has a field rule to subtract sales from current inventory

    extending the concept would lead to

    a receivings table with a field rule to add receipts to current inventory

    At that point you do not need a set?
    There can be only one.

    Comment


      #3
      Re: Inventory

      But in AlphaSports I have been looking for the code that does the calculation for qtyonhand in the products table and cannot find it.

      Comment


        #4
        Re: Inventory

        Posting in field rules will do it.

        Comment


          #5
          Re: Inventory

          But with a posting field rule, wouldn't the post be done every time a record is updated. Our order table has several fields that are updated several times before it is closed. Would that mean that the inventory would be deducted each time the record is updated?

          Comment


            #6
            Re: Inventory

            Not sure what updating a record means in your case.

            The field rule should fire once when the record is first saved and then each time the record is edited.

            You can always write your own posting routine in the field rules, field events.
            There can be only one.

            Comment


              #7
              Re: Inventory

              The inventory will only be updated if the invoices qty field is modified (the amount is changed).

              Comment


                #8
                Re: Inventory

                I think I am liking the two table idea better. If I understand the process, when the order is posted, the quantity that is used by the order will be deducted from the quantity on hand. If the quantity on the order is adjusted, the new amount will also be deducted from the quantity on hand. So if the original order was for 5 items and the customer decides they want to change the order to only 4 items, after the order is updated, between the original post and the update, 9 items will be deducted from stock on hand.

                Am I totally lost?

                Comment


                  #9
                  Re: Inventory

                  Originally posted by wizurd View Post
                  I think I am liking the two table idea better. If I understand the process, when the order is posted, the quantity that is used by the order will be deducted from the quantity on hand. If the quantity on the order is adjusted, the new amount will also be deducted from the quantity on hand. So if the original order was for 5 items and the customer decides they want to change the order to only 4 items, after the order is updated, between the original post and the update, 9 items will be deducted from stock on hand.

                  Am I totally lost?
                  In a word - yes - ;)

                  Try it, you'll like it.. In your scenario, the 5 will be deducted, then when it's modified to only 4 items, the inventory level will be adjusted by the difference and 1 will be added back into inventory.

                  But don't take our word for it. Set up and example and work through it..
                  Al Buchholz
                  Bookwood Systems, LTD
                  Weekly QReportBuilder Webinars Thursday 1 pm CST

                  Occam's Razor - KISS
                  Normalize till it hurts - De-normalize till it works.
                  Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                  When we triage a problem it is much easier to read sample systems than to read a mind.
                  "Make it as simple as possible, but not simpler."
                  Albert Einstein

                  http://www.iadn.com/images/media/iadn_member.png

                  Comment


                    #10
                    Re: Inventory

                    I don't think you're lost.

                    You shouldn't allow changes to an invoice once it is created. You do allow modifications/corrections by having a means to enter a plus or minus quantity adjustment by item. The posting of that quantity will correct the inventory.

                    The invoice itself will need to be designed to group by item and all of the invoice product fields, except the invoice quantity, will be put in the group header (no detail section). The invoice quantity field will be a total of the individual detail lines. If there are no modifications you get the original invoice values. If there are modifications you get the net invoice values.

                    Nothing wrong with your original idea where you have multiple tables and a set, just offering an alternative.
                    Last edited by Stan Mathews; 06-09-2009, 01:11 PM.
                    There can be only one.

                    Comment


                      #11
                      Re: Inventory

                      Thank you all. That is awesome. Is there somewhere that keeps track of the calculations or it just handles it.

                      Comment


                        #12
                        Re: Inventory

                        To Wizurd:

                        My way of handling this, is to have in my inventory table, the following fields: "Start_bal"; "Qty_in": "adjust_qty", "qty_out"; "Bal_on_hand" My inventory has a calc field rule for{ "bal_on_hand" = {"start_bal" + "qty-in" + "adjust_qty" - "qty_out"}}

                        In a separate PASSWORD PROTECTED ADB, an "Adjust" table has a form with the following fields, "employee id" -- "date" -- inventory item (from a lkup) -- qty --
                        reason.

                        The qty field posts to the "adjust_qty" in the inventory table as a positive or negative number.

                        The password protected adb maintains records of each posting, by whom, when and for what reason.

                        Hope this is of some value.

                        John Linley

                        Comment

                        Working...
                        X