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

Calculate on hand stock but also keep track of different locations

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

    Calculate on hand stock but also keep track of different locations

    I have chewed on this one for a while but I'm stuck. How can I update the qty in my storage location when a transaction takes place.

    Each item can be stored in different pre determined locations and I need to keep track of how many are in each location.

    Thanks
    Attached Files

    #2
    Re: Calculate on hand stock but also keep track of different locations

    I didn't look at your zip file, but this should be easy, with the following warnings:

    say you have locations WH1, WH2, WH3, WH4 (WH is for warehouse, or similar)
    each of these is a field in the inventory table, with another field, OH (on hand)
    where OH is a calculated filed, the sum of the locations.

    If you only have one user entering records, no problem. But if you have several users entering data you will need to do the following:

    DO NOTuse posting for the inventory

    In an Invoicing system, for example, where you are entering line items for items purchased - in the cansaverecord event in the lineitems table field rules, open the inventory table in exclusive mode allowing may 5 trys with a 1 second interval, and deduct or add the the quantity where purchased from, and then close the inventory table.

    Although not technically necessary, when you have maybe 5 users who are entering invoices and are very quick, this will overcome isues.
    Last edited by martinwcole; 07-08-2013, 08:27 PM.
    Cole Custom Programming - Terrell, Texas
    972 524 8714
    [email protected]

    ____________________
    "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

    Comment


      #3
      Re: Calculate on hand stock but also keep track of different locations

      Hi Emile,
      Have you tried a posting field rule for each of the transaction table fields Quantity_Received and Quantity_Used? If you match the storage_id in both tables it seems to work fine.

      Sorry Martin - we seem to have overlapped our responses - I will defer to you.
      Robin

      Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

      Comment


        #4
        Re: Calculate on hand stock but also keep track of different locations

        Hi Mo,
        No problem, but I should have added, "if you are fluent with writing coded in xbasic."
        Cole Custom Programming - Terrell, Texas
        972 524 8714
        [email protected]

        ____________________
        "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

        Comment


          #5
          Re: Calculate on hand stock but also keep track of different locations

          Emile,

          The method you appear to be trying to employ is entirely possible, and for some situations, preferable;
          (examples;- different stores, pricing varies, ordering done at branch level, number of branches or users want to add locations for other purposes).
          That being, essentially, an inventory master record for each location. Your design maybe overly complicated - too normalized in my opinion. And multiple maintained consolidations. If you DO need to use this method that can be discussed. I have such a system in use by dozens of businesses for over a decade.

          Without a doubt Martin's scenario is much simpler and most popular.
          Where a single record is used per stock item with a finite number of fields per branch to carry the stock quantity on hand at each.
          From your example that is all you are trying to achieve.
          Last edited by Ray in Capetown; 07-09-2013, 03:38 AM.

          Comment


            #6
            Re: Calculate on hand stock but also keep track of different locations

            We do this a lot as well sell several different types of inventory apps. What I like to do is use the Post to Inventory field rule. When the user enters the item or stock number for an item being added to inventory we do an auto op up or drop down list showing the item at all its locations. The user can select the line with the item and enter the Qty field and it will remove the Qty of the item selected. Thi method also gives each user the ability to see how many of these items are in inventory. It also allows a user to see that the slot or bin location may not have enough of the items and keeps from running into a negative stock in one location while also having an incorrect amount in another.

            We also added a transfer option that allows the user to move a quantity of the item from one slot to the other.

            Comment


              #7
              Re: Calculate on hand stock but also keep track of different locations

              Hi there. Thank you for all your replies. I have thought about all off your ideas. I first tried posting like Robin suggested before I made this post but that didn't work. It seem to have work but it updated only the first storage KEY field found in the child table if there are duplicate records which there will be. I might have more than a 100 different storage boxes so Martin's idea won't work for my application but only one user will be entering information. Thank you Ray but I'm not planning a complicated database like that. The database is meant for one location with multiple storage locations and one user.

              I have though come up with another solution and it seemed to do the trick for now. Since both tables have the same ITEM_id and Storage_id I have created a calculated field in both tables adding these to fields together in each table and adding a character to it just to make the record unique I.e item_id+"x"+storage_id.
              Now I can post the amount from the transaction field to the correct storage location and to inventory on_hand field.(I have created a lookup field with a filter in the transaction table to ensure that the user can only select the storage locations that are pre-determined in the child table for the specific inventory item. The lookup then also show the qty in each location. (Thanks for the idea Fred). It will be quite helpful to see which locations are running low.

              Comment


                #8
                Re: Calculate on hand stock but also keep track of different locations

                Sounds good.
                Presuming "x" is an incrementing string or number?

                Comment


                  #9
                  Re: Calculate on hand stock but also keep track of different locations

                  no no, X is just x. Just a character that helps make the new key field unique to every storage location for that specific item.

                  Comment

                  Working...
                  X