Fields update depending on a Value List, how to ??

[TougToug]

Hi,

I have the same problem in all my Layouts, i set up some fields or a whole portal to be dependant on 1 or 2 or 3 particular fields and for some reason (i suppose my relationships are not correct or something else i don't know) the dependant fields don't refresh automatically (i only need to click on layout mode and back on browse to update them)

Example:

if i put a value in "Project" then i choose a part from "part#" drop-down list and normally my portal should clear up (if there is no info for this part) and display the info relevant but doesn't

another one, i choose a project, i choose a part# and this display my jointId, my 2AId, my TubeId, but not the FirTreeId (which is only directly linked to the 2AId),

I am quite a newbie on FMP, managed to sort out few of my earliest problems but there i'm hitting a brick wall!! Can somebody help??

Thanks

TestVerificationDatabase.zip

[-Queue-]

The first part appears to be working fine. Have you upgraded to v3?

For the second part, you need a script step to Refresh Window [Flush cached join results], because your FirTreeId is dependent on related fields in Part Details being updated so that the Joint relationship refreshes.

Or you can try this trick, which seemed to work for me. Create a calculation field in Part Details equal to Joint::FirTreeId. Then, delete it. Now close Define Database and go to your Lab Data layout. Try changing your part# and see if FirTreeId updates now.

[TougToug]

Thanks for the help, although the little trick doesn't work for me, i am gonna look into the RefreshWindow sript step... (wondering how to do it without using a button tho ??)

Great Forum, lots of help !!

[Søren Dyhr]

Create a calculation field in Part Details equal to Joint::FirTreeId. Then, delete it. Now close Define Database and go to your Lab Data layout. Try changing your part# and see if FirTreeId updates now.

I is it strictly 7.0 methodology? - have a sneeking suspicion that it's exactly what...

http://www.filemaker.com/downloads/pdf/techbrief_fm7_foundations.pdf

...is saying on page 34, when:

If the first relationship in the path used to get from the portal record

[-Queue-]

See if the attached file works for you. It's still working for me, even after closing it, shutting down, restarting, and reopening it. When I change Part#, FirTreeId updates immediately.

TestVerificationDatabase.zip

[TougToug]

Thanks Queue

Great Job, i have no idea why it didn't work when i tried but now it works perfectly fine with your file, thank you so much again

Now just need to make my portal update in the same knid of way in the Project sheet(test) Layout

Cheers

[-Queue-]

Are you wanting to change the Project ID and Part # to update the portal? If so, you won't want Part # to be Test Data::Part # or changing it destroys the relationship. I would think you'd want it to be a global that's related to Test Data::Part # so that you can change it to view the different related Test Data records without changing the value in either Test Data or Lab Data.