I am working with FileMaker Pro 6.0.
I have a prices file that contains a unique name field, a size field, and a price field, among others. Each unique name may have multiple sizes and prices.
For example:
record 1: abc, 1inch, $1.00
record 2: abc, 1.5inch, $1.50
An inventory file has a unique name field, a quantity field, a size field and a location field, among others.
For example:
record 1: abc, 10, 1inch, 3
record 2: abc, 10, 1.5inch, 5
I need to determine the total value (price) of all the records in the inventory file.
If the correct price for each record can be displayed in a field in the inventory file, I understand that it would be a simple matter to make a calculation field that multiplies that price by the quantity. Then a summary field, based on that calculation field, could be made for all the records.
This is a model of the problem. I would apply the solution to my existing relational data base which I use for production planning and billing, among other things.
In that data base the name field has been the basis for most relationships. We use horticultural taxonomy and all names are unique. Most names have 3 or 4 size/price values.
I’ve tried to simplify the example to illustrate the problem.
I have a prices file that contains a unique name field, a size field, and a price field, among others. Each unique name may have multiple sizes and prices.
For example:
record 1: abc, 1inch, $1.00
record 2: abc, 1.5inch, $1.50
An inventory file has a unique name field, a quantity field, a size field and a location field, among others.
For example:
record 1: abc, 10, 1inch, 3
record 2: abc, 10, 1.5inch, 5
I need to determine the total value (price) of all the records in the inventory file.
If the correct price for each record can be displayed in a field in the inventory file, I understand that it would be a simple matter to make a calculation field that multiplies that price by the quantity. Then a summary field, based on that calculation field, could be made for all the records.
This is a model of the problem. I would apply the solution to my existing relational data base which I use for production planning and billing, among other things.
In that data base the name field has been the basis for most relationships. We use horticultural taxonomy and all names are unique. Most names have 3 or 4 size/price values.
I’ve tried to simplify the example to illustrate the problem.