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

Finished Goods to Stock Database Design

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

  • MoGrace
    replied
    Re: Finished Goods to Stock Database Design

    Hi Robert,
    Originally posted by SWWeatherGuy View Post
    Haha, yeah, FIFO is what we typically try to do but not going to the trouble of marking the eggs. Once they are accounted for "in stock" it doesn't matter which specific egg it is, only which bird it came from. Actually, the "finished product" is the egg once it's collected and cleaned and that's what I want to log daily as it's added to the EggStock. At that point, the eggs can be "invoiced" out of stock to a cake, cookies, sandwich, or any number of delicious things, haha. I sell a few dozen to help offset feed costs too. I'm trying to put together a db more just for something to tinker with in Alpha, not so much because it's really needed.
    Tinkering with something you know about is a good way to get started in A5. Tracking the eggs produced is just the beginning. Like I said, it does sound like a fun project. You can raise a few chicks, track your expenses and your sales and just about anything in Alpha as it comes to mind. A project like this will grow almost by itself!

    Leave a comment:


  • SWWeatherGuy
    replied
    Re: Finished Goods to Stock Database Design

    Originally posted by DaveM View Post
    probably chicken in table
    eggs in separate table and connected to the chicken table in a set.
    That would be a start anyhow.
    for stock(eggs) another table where you have sent out posted and each egg adds to the stock.

    When I was a kid, we had a small egg farm(along with the other)
    we simply picked uip the eggs and marked a date on a paper above the chicken. If a chicken did not lay one for a week, we ate it.
    Thanks for the reply. Yeah, even though the chickens are as much pets and a hobby, if they're not laying I'm not gonna keep them around long. Mine aren't caged so the only way I know which egg is from which bird is the variety of birds I have and knowing what kind of egg each produces.

    So, basically your suggestion is to treat it along the same lines as, say, a product/parts invoicing design, but maybe in reverse since instead of leaving stock, the eggs are being added to stock? I was thinking of the daily log of collected eggs consisting of a form, simply with a check box next to each bird (layed or didn't lay each day.) I wanted that to be dynamic so if I add more birds, they are already included on the collection form. I guess that could be accomplished with a one-to-many link and an associated browse object? Thanks, again.

    Leave a comment:


  • SWWeatherGuy
    replied
    Re: Finished Goods to Stock Database Design

    Originally posted by MoGrace View Post
    Sounds like a fun project. Are you planning on doing a FIFO for the eggs? How many days will you keep an egg in stock before moving it to the finished product - which I suppose could be a cake or another chicken?


    Haha, yeah, FIFO is what we typically try to do but not going to the trouble of marking the eggs. Once they are accounted for "in stock" it doesn't matter which specific egg it is, only which bird it came from. Actually, the "finished product" is the egg once it's collected and cleaned and that's what I want to log daily as it's added to the EggStock. At that point, the eggs can be "invoiced" out of stock to a cake, cookies, sandwich, or any number of delicious things, haha. I sell a few dozen to help offset feed costs too. I'm trying to put together a db more just for something to tinker with in Alpha, not so much because it's really needed.

    Leave a comment:


  • DaveM
    replied
    Re: Finished Goods to Stock Database Design

    I keep thinking the chickens and the eggs can be represented in the same table since, in my case, I know which eggs come from which birds. Maybe I'm not thinking something about that right, though.
    probably chicken in table
    eggs in separate table and connected to the chicken table in a set.
    That would be a start anyhow.
    for stock(eggs) another table where you have sent out posted and each egg adds to the stock.

    When I was a kid, we had a small egg farm(along with the other)
    we simply picked uip the eggs and marked a date on a paper above the chicken. If a chicken did not lay one for a week, we ate it.
    Last edited by DaveM; 11-17-2015, 11:37 AM.

    Leave a comment:


  • MoGrace
    replied
    Re: Finished Goods to Stock Database Design

    Sounds like a fun project. Are you planning on doing a FIFO for the eggs? How many days will you keep an egg in stock before moving it to the finished product - which I suppose could be a cake or another chicken?


    Leave a comment:


  • SWWeatherGuy
    started a topic Finished Goods to Stock Database Design

    Finished Goods to Stock Database Design

    I'm having a tough time rapping my brain around an efficient way to design tables and sets to track the daily moving of finished goods (eggs) to stock or product inventory, and am hoping someone has a good suggestion. Specifically, it would be used to track chicken egg production. I've designed a few tables, including a "Chicken" table, with all information pertaining to each bird, including a field (EggCount) to track total production for the life of the bird. Even though the egg is the "Finished Good" I keep thinking the chickens and the eggs can be represented in the same table since, in my case, I know which eggs come from which birds. Maybe I'm not thinking something about that right, though.

    Essentially what I want to design is a database that I can log one record per day, indicating which bird layed an egg that day. During that entry I want to post a 1 egg increment in the "EggCount" field (historical total) in the "Chicken" table, for each bird that layed that day. At the same time, I want to increment the stock quantity of each egg layed in my "product stock." I don't know why I'm having such a hard time visualizing this design. Can I simply add a "Qty-In-Stock" field to my "Chicken(&Egg)" table, post any daily increments there, then calculate the total in-stock from that field for each bird? If so, can I just have a one-to-many set with the "Chicken" table and whatever table is used to record the daily layers?

    Thanks, maybe something will click overnight.
Working...
X