product inventory for multiple locations

  • Thread starter Russ via AccessMonster.com
  • Start date
R

Russ via AccessMonster.com

Help!!!
Need to make a database to help control product inventory for multiple
locations, what suggestions can anyone provide?
 
D

David C. Holley

I would use a summary and a detail table to monitor the inventory. The
detail table would contain the specifics per location, the summary table
would contain the total inventory
 
R

Russ via AccessMonster.com

Ok, so I would a product table with part number, description, cost etc.. Then
have a product location table with location id, on hand order level and order.
Is this what you are suggesting, is this the best way?
 
R

Russ via AccessMonster.com

Would that not make a very large table?
If I have 1000 products and 3 locations the location table would have 3000
records.
Ok, so I would a product table with part number, description, cost etc.. Then
have a product location table with location id, on hand order level and order.
Is this what you are suggesting, is this the best way?
I would use a summary and a detail table to monitor the inventory. The
detail table would contain the specifics per location, the summary table
Click to expand...
[quoted text clipped - 3 lines]
Click to expand...
 
P

PC Datasheet

How about ---
TblLocation
LocationID
Location

TblProduct
ProductID
PartNumber
Description
UnitCost

TblLocationInventory
LocationInventoryID
LocationID
ProductID
Inventory
EconomicOrderQuantity


--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
[email protected]
www.pcdatasheet.com

If you can't get the help you need in the newsgroup, I can help you for a
very reasonable fee.
Over 1000 Access users have come to me for help.
Need a month calendar or 7 day calendar? Contact me.
 
R

Russ via AccessMonster.com

Thanks PC Datasheet, that is something like what I have, maybe I am missing
something. Would that not make a very large table? If I have 1000 products
and 3 locations the location table would have 3000
records? Would this be slow?

ProdID Location
123 Location A
Location B
Location C

125 Location A
Location B
Location C
 
D

Duane Hookom

It should not be slow. Make sure you set up your relationships so the proper
indexes are created.
 
Top