database design/relationship

[jozino01]

hi,

i want to create an access database for wood processing company; its operation is simple - they buy raw logs and cut them into lumber (lots).
some lots are sold directly, some lots are resaw.
outturn from rerun is sold or part of it goes for rerun again, etc.

i am not sure what would be the best way to treat lumber for resaw/rerun since some lots can be rerun a few times...

any idea, please?

 

[fneily]

What kind of information do you want to keep? Is each raw log individually marked? Are there various lot Sizes or Shapes and a quota for each? Is there actually a distinction if it's a raw log or a rerun - a log is a log? Does the number of reruns matter?
Other things your database can do - your plant probably has different departments so if a piece of machinary breaks, it'll affect other processes. You could set up a tracking and notification system which goes across department lines with your database. I created one for a national dry wall company called National Gypsum.
Maybe you could tell us exactly what you want to track and report on.

 

[jozino01]

sure. it's even simpler - this company has no machinery, they just use diffent mills so my problem is just incoming wood (logs), cutting cost, outturn lumber.

i have table LOGS (for raw logs):
BOOMID BOOM VOLUME PRICE-M3 TOTAL CUTID
1 CGHLB 68-141 1535.6 $117.00 $179,665.20 1
2 ABHLB 5-137 1828.8 $110.00 $161,168.00 1
3 BRHLB 6B-29 1473.7 $117.00 $172,422.90 1
...

table CUTS (cutting cost and misc. charges):
CUTID NUMBER CUTDATE CUTCHARGE MISCCUT RERUN TRUCKING COMMISSION DUTIES SCALING TOWING
1 JAG 5-25 5/01/06 $308,303.79 $24,821.07 $0.00 $9,405.88 $4,000.00 $0.00 $4,271.66 $14,238.86
...

table OUTTURN (for lumber/lots):
LOTID CUTID SIZE GRADE LOT VOLUME PRICE REVENUE PERCENTAGE INVOICE CUSTOMER
8 1 12 X 12 (20) 2 MER & BTR JGH 4200 24960 $560.00 $13,977.60 1.91% 988 SOUTHBEACH-9348
...
if the lots goes to rerun there is no INVOICE and CUSTOMER (empty fields)

so far i have no problem (in my opinion) to link/create relationship everything by cut#

rerun lumber would be similar to OUTTURN table. lumber/lots from outturn have diferent lot name and size. more lots can go to rerun and be resaw into diferent number of new lots.