Re: Coping with Ingredients

Yes, I was thinking of doing that. However I must have the ability of being able to change the rate for any ingredient. So I'm thinking of having a SuggestedAppRate field in tblMaterials, and an AppRate field in tblIngredients, and setting the default value of AppRate to that of SuggestedAppRate, so that it can be accepted in normal circumstances, or changed in others. Oh! Wait. I think I tried something like that before, and found that I can't change the default value of a field once a field in the record has changed (in this case, the MatID). Is this right? I'm going to have a play with this. If this does happen, is there a way around it?

Thks,
Graham

"Steve" <santus_at_penn.com> wrote in message news:MfPN8.2587$bf7.1798_at_newsread1.prod.itd.earthlink.net...
> Graham:
>
> I suggst you move the AppRate to the Materials table; AppRate is
> as an attribute of the material. TblIngredients represents a list
> of the materials applied to each section of the building.
> TblIngredients is a resolver table for the many to many
> relationship between TblMaterials and TblSection. You have many
> materials applied to many sections.
>
>
> --
> PC Datasheet
> A Resource for Access, Excel and Word Applications
> resource_at_pcdatasheet.com
> www.pcdatasheet.com
>
> · Design and basic development for new applications
> · Additions, Modifications and "Fixes" for existing applications
> · Mentoring for do-it-yourselfers who want guidance
> · Complete application design and development
> · Applications Using Palm Pilot To Collect Data And
> Synchronize The Data Back To Access Or Excel
Received on Wed Jun 12 2002 - 17:30:18 CDT