Orkut Gmail Calendar Documents Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Message from discussion Inventory DB
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Donald J Kinney  
View profile  
 More options Feb 14 2000, 1:30 pm
Newsgroups: comp.databases
From: "Donald J Kinney" <kin...@ndak.net>
Date: 2000/02/14
Subject: Re: Inventory DB

Mark L. Breen <m...@solution-providers.ie> wrote in message
news:38a3d353@royan.d-n-a.net...

> Hello All,

> My questions is regarding the structure of a database that
stores inventory.

> I have two types of transactions, one the increases the
effective inventory
> level and one that decreases the effective levels.  To

calculate the actual
> inventory level, I can sum all the increases and subtract
from that all the
> decreases.  This would give me my inventory balance.

> Obviously, that query could get quite slow, so it is

desirable to store the
> actual balances in an inventory table.  This would give
you an immediate
> record of what is in stock for a particular part.  I am
considering
> including an Adjustments table.  This will basically keep
track of the old
> balance, the adjustment and the new balance.

> My question is how do you guys handle this kind of stuff?
Is there a
> recommended way to handle inventory?  I am nervous that I
will end up with
> the calculated stock not being equal to the static stock.
I know I am
> breaking the rules of normalisation by storing a

calculated field, but even
> the banks use this tactic.

> You advice will be much appreciated.

> Thanks in advance,

> Best Regards

> Mark Breen
> Solution Providers Ltd
> Ireland

Keep one database with records for the different parts with
two fields for each period of time one for Items received
and one for Items sold. Also have a Total on Hand field and
of course the part number fields.  Using months as your time
period you will have a total of 26 fields.
This will also give you a way to see how fast the turn
around on the parts is.  You will see when you received the
parts and the time it took to sale the parts before
reordering.
Update the total field either daily or when you receive sale
the part as part of your program.

Donald


    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2010 Google