Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / General 2 / January 2008

Tip: Looking for answers? Try searching our database.

Manufacturing Inventory Database

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Long - 29 Jan 2008 01:21 GMT
I am trying to create a database that will be able to track inventory of
products that are used to make up different items. Basically we are building
items from a series of individual products. Not all the finished items will
be made up of the same components, but some will use like items. I have
looked at the Inventory template, this seems to be useful for the individual
product components, but how do I create the new finished items.  I thought
about using Parent ID's for these items, but am stumped since many of the
same products are used to make up the individual items. These will be the
items that will be purchased/leased/or rented.  I will also like to
incorporate customers/orders into this database.  When a customer orders a
particular item, I would like the inventory of individual products that make
up the item to be reduced. Any ideas?  One other comment, the items that the
customers purchase will have unique serial numbers, so we can track and
monitor the items. Am I making any sense to anyone? Is this all logical to do
in access? Thanks for any help anyone can give.
Signature

Long

rico - 29 Jan 2008 13:37 GMT
Long,

This is what access was made to do. The structure would take too long for me
to write out here, but the basic method, is that you have a table for
products, table for subproducts, table for subsubproducts and so on. in
subproducts you have a field to say which produt it is for, and in
subsubproducts you have a field to say which subproduct it is for. THis is
whats called a one-to-many relationship. I suggest you read up on this and on
access in general and how to structure it should become fairly obvious.

O and have a look at the northwind database, which comes with access, it is
a perfect example of a ordering/parts database

> I am trying to create a database that will be able to track inventory of
> products that are used to make up different items. Basically we are building
[quoted text clipped - 11 lines]
> monitor the items. Am I making any sense to anyone? Is this all logical to do
> in access? Thanks for any help anyone can give.
Long - 30 Jan 2008 01:24 GMT
Thanks.  If I have additional questions will you be willing to work with me?  
Signature

Long

> Long,
>
[quoted text clipped - 24 lines]
> > monitor the items. Am I making any sense to anyone? Is this all logical to do
> > in access? Thanks for any help anyone can give.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.