You could simplify this by having just one database with two tables
one table called " Client Input " in which you have a field name " Part Number "
then you have a second table called " Part-List" in which you have a field called " Part-Number " and another field called " Part-Name " and another field called " Part-Description
and perhaps another field called " Part-Cost "
Then you do a relationship using the field "Part Number " and " Part-Number " joining both tables
After that in your " Client Input " layout you can put the field part Number and then put the fields from the second table on that layout such as Part-Description and
whenever a client enters the part number automatically the Part-Description will pop up
1) In PART-LIST, create a value list. Should be based on the contents of the table, using Part Number as the first field and Description as the "also show data from second field" field.
2) In REPORT, add a table occurrence to your graph from an external FileMaker data source. Point this to PART-LIST.
3) Create a relationship between Part Number in REPORT and Part Number in PART-LIST.
4) In the Manage Database dialog in REPORT, set the Description field to auto-enter a Lookup from PART-LIST.
5) Create a Value List in REPORT that uses a value list from another file, in this case, PART-LIST. Use the value list you created in step 1.
6) Attach the value list you created in step 5 to the Part Number list in REPORT.
That is all.
Edit: And Luc is correct about consolidating the tables and just using a related field. In fact, you could just use the related PART-LIST::Description field on your layout even if you don't consolidate your tables and do away with the REPORT::Description field. It's probably a better practice to do so.