Re: Database design ideas or templates...

romantercero_at_gmail.com wrote:

>
> The basic requirements for the database are that it store transactions
> made so that to get a current inventory count need to add up the
> inbound and outbound transactions. This is to say that it be auditable.

The trick here is to put your attention and effort into the TRANSACTIONS table, the list of inbound and outbound transactions. Always derive the final tally from the transactions. When the physical count is different, as always happens, you make adjustments by putting entries into the TRANSACTIONS table. This makes everything auditable.

> Another requirement is that products cane come grouped and can be
> manipulated with one group ID or handle for convenience but in outbound
> transactions it should be possible to send only a unique product from a
> group.

This is a little vague to answer on a newsgroup. Packaging and grouping of items can all be tracked in tables of course, but without more detail it would be hard to answer here.

-- 
Kenneth Downs
Secure Data Software, Inc.
(Ken)nneth_at_(Sec)ure(Dat)a(.com)