Well... I spent about two weeks of trial and error getting my DB to provide conditional value lists as I wished, since I couldn't post the DB online. After using the DB for a week (mostly flawlessly), my conditional value lists didn't end up working. Being frustrated after beating my head against the wall for so long, I researched (more) about this ability, and have come to the conclusion that either 1) I have issues translating simple two table examples to my more complex example, 2) I'm missing something fundamental, 3) my structure isn't conducive to my goals, or 4) I have issue with creating the value lists from the proper sources (which is easy to do, considering the multiple table complexity).
As a result, I created a greatly simplified and sanitized version of the DB (only containing the sections in question) and would GREATLY appreciate a Filemaker veteran's insight into how I could do this. The relationship graph of the DB file has notes that explain the desired outcome. I am just at a loss for words really; I've cursed FM relentlessly lately, hahaha.
Thanks in advance for any push in the right direction. I'm not looking for someone to outright solve my issue, but would really appreciate something that puts my mind on the right track, as my logic obviously doesn't jibe with FM.
Thanks again!
Flight Equipment Measurements (Simplified).fmp12
EDIT: I will make a copy of the above example file to show how the parts are related as of now (not that the relationships are correct, but I was able to ALMOST get it to work...). In addition, I will add notes to the updated file to show how the value lists are put together. Maybe it is just a simple thing to correct (although I AM more interested in starting fresh, the CORRECT way, versus my trial and error...).
EDIT 2: Well... After creating the extended (as constructed in my DB) example file, I've found that everything works as it did during my testing. So... It appears that subsequent relationships that I created after this section (in order to view reports/other related data) have mucked with the relationships in this section. Now I have to try and figure out which relationship is causing the problem, and attempt to design it out, while keeping the functionality in the rest of the DB. Ugh...