What you need are these relationships:
Final::BrandID = Model::BrandID
Final::ModelID = Part::ModelID
Final::PartID = Final::PartID // this last relationship is not needed for the conditional value lists, but you probably need it for other uses.
In each case, the conditional value list filters values based on the value you enter or select in a Record in the Final table, so you need to use relationships that link to fields in the Final table.
Thanks for the answer, its beggining to make sense.
In any case, I can't even get the parent drop down (Brand) to populate itself with ANY values now. Do I have to "refresh" the file once I do these relationship changes?
The drop down for brand should not be a conditional valuel list as this is the first value list that drives the process for the subsequent conditional value lists. It should just list all Brand IDs from the Brand table.
You can related two tables in FileMaker with as many different relationships as you need. You can also relate a table to itself in a relationship. The secret is in the term "Table Occurrence". Open Manage | database | relationships. Each "box" in this chart is a table occurrence that points to a data source table. Both the Table Occurrence (TO) and the data source table start out with the same name when you first define tables in your file, but you can actually double click these boxes and rename them any way you want. You have buttons at the bottom where you can add a new table occurrence and then select it's data source table. This table can even be a table in a different FileMaker file. You can also select a TO by clicking it, then click the button with two green plus signs and you'll get a copy of the TO you selected with a number after the name, but referring to the same data source table.
Thus, you can click Final, click the plus signs button and you'll get Final::PartID = Final 2::PartID. If you look on the Tables Tab, you'll see that you now have two "occurrences" of Final, named Final and Final 2.
Here's a tutorial on table occurrences you may find helpful: Tutorial: What are Table Occurrences?
Good tutorial Phil. Learned another new trick, have been trying to think of a way to do that with the contactDB tables. Thanks!
Oh I see. Never thought about that. I will deff look into that tutorial.
So, even without relating the tables the conditional ones will "track through" just using the serial numbers? I've just done that and now my Brand has populated, but it doesn't seem to track through to the other ones.
I've set up the related vales (for Model and Part #) to be related fromt he table above i.e. Model starts from Brand and Part starts from Model, or am I setting that up wrong?
Cheers, sorry for the hardhead-eness, I'm learning this as I go along and I've never dealt with databases like this before!
You'll need the first two relationships to establish the conditional value filtering so that brand limits the list of models (Final::BrandID = Model::BrandID ) and Model limits the list of parts (Final::ModelID = Part::ModelID).
But, don't I have to relate the Brand table to any othe table? In my relationship manager that table is floating without anything attaching itself to any others...
I was under the impression all tables have to be related in order for serial numbers to "track through" to other tables. Right now my Brand drop down menu is set to Include All Values and its populating fine, but the other just give me a blank box. I'm wondering if either I'm setting my serial number/relationships wrong, or the "related vallues starting from" wrong.
You may indeed need those relationships for other reasons but not for the conditional value lists requested in this thread.
A link from Final to Brands, (Final::BrandID = Brands::BrandID, for example), could let you display or look up data from the brands table on your layout, but it's not a part of the process that displays your conditional value lists.
I see. Well its strange that I still can't get any values for the other 2. No idea where I've gone wrong with this thing!
Thanks for all the insight though, much appreciated, I've learnt quite a lot.
The relationships look correct. If you aren't getting any values in the value lists for Models and Parts, then something is not set up correctly in the set ups for these value lists or in the data types of the fields used to define the relationships.
The conditional value list for Models, should list ModelIDs from Model, include only related values starting from Final. Final::BrandID and Model::BrandID should be the same data type (both type text or both type number.)
The conditiona valeu list for Parts should list PartID's from Parts, include only related values starting from Final. Final::ModelID and Model::ModelID should be the same data type (both type text or both type number.)
Yeah still nothing. The only thing I have noticed is that some of the ID fields have Indexed in the Database Manager....could that be affecting this somehow?
Man how can this little tiny database be such a pain in the @ss??
Indexing is required on the "many" side in order for relationships to work. Including a field in a relationship will turn on it's indexing if it is not specifically disabled or is a field that cannot be indexed.
Thus I'd be concerned if Model::BrandID or Parts::ModelID where NOT indexed.