Hi everyone, i know i already posted something similar but still cant get it to work properly.. it improved and i understand it a lot better, but still need help:

here is the problem, i have fields and a portal that depend on two fields:

"part#" and "test" these 2 fields are value lists with "test" depending on "part#"

so far when i change the value in "part#", the data refreshes immediately, but when i change the "test", nothing happen...

if anyone could have a look at my database, and give me some advice that would be very nice

Thanks, and again GREAT forum !!!

Copy(2)ofTestVerificationDatabase.zip

I have a similar problem and I wanted to look at your file, but I think that it is in wrong format, because I can't open

Well it must be you because i can download it and open it from work and at home...

sorry about that

:'(

The relationship from Lab Data to Test Data does not include Test ID, so changing the Test ID in the related Specification field will have no effect on the Test Data portal.

Yes i thought about it, but when i add "testId" in the relationship, i end up with only 1 test available, and if i try to add more in the TestData portal, it doesnt work (they are not being saved)...

Any ideas why?

Did you change the TestID field on your Lab Data layout to be based on the current table instead of the Specification one?

Did you change the TestID field on your Lab Data layout to be based on the current table instead of the Specification one?

yes indeed! (sometimes i impress myself :-))

see the attached file for the latest release, i know it hasnt changed much but i'm getting really annoyed with it and sometimes starting to think it might be just a graphic refresh that is not done properly by the computer... Because sometimes it refreshes straight away, and the next second doesn't

Let me know if u think of anything

Sorry for being a pain but i'm a newbie (started using filemaker and actually any database software about 1 or 2 months ago)

THANKS A LOT ! !

TougTougV2.zip

I think you'll want a different relationship for your Test List value list. The original one should work, so that when the Project and Part# are selected, the related Test IDs are available from the list.

It appears that you've changed the main relationship to be based on Test Details instead of Test Data, but the portal on the Lab Data layout still displays records from Test Data, which is currently an empty table.

Well that's just because i renamed the tables to give a bit more sense to the whole thing...

Now i tried to put some data in the portal, but when the relationship between "LabData" & "TestDetails" is based on the 3 fields ProjectId, Part#, and TestId, it works fine although i only have 1 TestId to choose from (checking in the Project Sheet(test) layout, the portal only displays one as well, but the records still exists in the TestDetails table)

And when the relationship is only based on 2 fields ProjectId, and Part#, it won't let me put any records in the portal on the LabData layout (This field cannot be modified until "TestId" is given a valid value)

In addition now that there is records in the portal i realized that when i change the TestId, the records in the portal stay too (they should disapear since they are supposed to depend on ProjectId, Part#, AND TestId

Here is my problem, hope i've been clear enough...

Thanks for your help ! ! !

Like I said, you need a different relationship for your Test Value list, one based on only Project and Part#, or else you will only have one option for Test ID, that being the currently selected one.

Since your portal is based on the Test Data TO, it doesn't matter what records are in Test Details, if they don't also exist in Test Data. In the last sample you posted, Test Details has 6 records, but Test Data has none.

I think it would help if you clarified what you are trying to accomplish. I still haven't been able to make complete sense of your goal or how you should have your TOs defined. We seem to be going in circles trying to solve a problem that I'm not sure is really a problem. It may just be that the relationships and/or tables are not efficiently constructed.

Definitly right Queue !!

I spent a bit of time on friday with someone that knows what he's doing, and i understood that all my relationships are wrong, so i built a new db almost from scratch changing the layouts to make them more consistent all the way and have a central table in the occurence graph, trying to make single relationship as much as possible, and using unique ID fields in each tables

Thanks for your help anyway, i'll probably post some more problems soon when i'll start writing some scripts or when i setup the privileges accounts

but for now i'm sorted (at least i think so..) so a BIG thank you to everyone

Later, aligator

TestVerificationDatabaseV2.zip

Now that is much more comprehensible. Nice job! I'm glad you got some good help to get you moving forward instead of around in circles. Good luck on the rest of it.

You know where we are if you need us.