RAW MATERIAL QUERRIES

[jen]

Hi, this is my first time on here. I am trying to create a database that
will enable the user to do querries on their product base. Any given product
has a number of raw materials, which have a solids % (which will need to be
calculated in another table), it will also a descriptorID, which I have in
anothe table now. The product will also have a specification, which is its
own table. Do I have to make the tables related in the edit relationship
area, or will it work without doing this? I am not sure where to drag and
drop my foriegn keys. Can this be done by using querries alone? They want
to do searches based on the DryWeight of a product, which each ingredient as
its own dry and wet weight.

first column: Each of the products ingredients wet weight should add up to
a 100% weight for a product.

Second column: This dry fraction is figured by taking an ingredients solids
% and multiplying it by its wet weight.

Third column: This is the dry weight of the total product once cured, it is
figured by taking the dry fraction divided by they wet weight, then
multiplied by 100.

Once I have this dry weight column figured I can start the querries.

I have tables:
Product
Formula
RawMaterials
Descriptor
Specs
Required specs

But when they enter a product in the Database should they enter it into all
the tables or can a query sort it to the proper tables?

 

[Michel Walsh]

But when they enter a product in the Database should they enter it into

all
the tables or can a query sort it to the proper tables?

If the tables are designed so that records can be re-used, there is only a
need to enter what is not already present.

As example, not often done in practice, but just for illustration, if you
enter the postal code in a record, there is, technically, no need to enter
the city name, neither the state name, *if* a table getting those
information, given a postal code, exists and *if* the used postal code is
already known in such table. So, ion this case, the table
"PostalCodesCityState" won't need to have a record added to it each time a
new "Client" is entered in the table of Clients. And you will be able to
retrieve the information through a JOIN between the two tables, in a query
(using the query, rather than a table, as foundation for your work).



Hoping it may help,
Vanderghast, Access MVP