Clive,
The more I thought about this the more I was pushed toward two tables. The only common field needed was Date. However I did use the idea of two seperate forms to populate the fields in one table. That worked great as well.
Thanks for you help.
Bill
Minneosota
--- In MS_Access_Professionals@yahoogroups.com, "Clive" <zctek@...> wrote:
>
> Hi Bill (Mn),
>
> You may be able to to do it with one table but I
> would recommend having two clearly distinct
> forms for Receipts and Distribution.
>
> Fields common to Receipts and Distribution, if any,
> should be in one table. Any other fields should
> be in tblReceipts or tblDistribution. That is the
> usual Normalization technique.
>
> The FoodInStock you can calculate by using a Query.
> If the FoodInStock weight does not tally with the
> physical stock when you do stocktaking then you
> need to add a record that details the discrepancy
> and adjusts the difference.
>
> Is there also a chance that you may be asked to add
> other fields later on?
>
> If you give us a list of all the fields we may be
> able to give a better answer.
>
> Regards, Clive.
>
> --- In MS_Access_Professionals@yahoogroups.com, "agent1of6" <Bill.Singer@> wrote:
> >
> > I am tracking the receiving and distribution of food from a Food Pantry. The tracking is just in pounds per day. I am not tracking individual items.
> >
> > I could set up a table to track receipts and another table to track distribution. Or I could set up one table to track both. Most of the fields I need on each table are the same but all of them. If I set it up to look like a checkbook then some of the fields will be left blank on each transaction.
> >
> > Which way is the proper way to do this? I can't see an advantage either way. Any advice you can give would be greatly appreciated.
> >
> > thanks
> > Bill
> > MN
> >
>
Tidak ada komentar:
Posting Komentar