database design?

[binaryop8]

Hi everyone/anyone?

I am trying to design and implement a [collection of] database. The content of these are based around trying to track 'widgets' in an exhibition system.

I would like to have a db [1] of the individual units and then the 'currently available number of these units'...

Some of these units are sent out to shows/projects [db2?]and when the show finishes they return to our warehouse [entered back into current stock]

I need to know on a daily/monthly basis what remaining stock I have available. [db3??]

any suggestions on how to efficiently organise/design this system?

Thanx in advance.

:qwery:

[comment]

Are these units recognizable individually, or is it just 3 of this, 6 of the other?

[binaryop8]

there will be 150 different specific 'units' - and a maximum quantity of say >1 <600 of each?

then the projects could be up to 5 running concurrently at any one time?

does this help?

[comment]

It seems very similar to this.

[binaryop8]

I'm just looking at that solution now - thanx [i'll let you know if it's adaptable for what I need] any other 'previous solutions' could help too...

cheers