gfilter in parent table – option for field- storage- use global storage…
Connect table pk e fk AND gfilter on campo che voglio filtrare
In Layout add field gfilter, radio button
Layout setup-script trigger – on layout enter add – set filter script – set field – gfilter “status”&¶&”stusb”&¶&”status”….
First observation from your screen shot of your relationships is that simply selecting the student ID will fail to properly link it to a record in the Student Class Gradebook Join Table. You need to also select a value for the class identification table.
Two time saving options you may find usefule:
If you select Duplicate Record while on a layout based on the Student Class Attendance Participation Computation table, you can create a new record with the same values in your two match fields and then you simply edit any other fields in this record to correctly record the data that you need for that student.
You can write a script that loops through a set of records in Student Class Gradebook Join Table that creates one new matching record in Student Class Attendance Participation Computation:
//after you perform a find….
Go to Record/Request/Page [first]
Set Variable [$StudentID ; value: Student Class Gradebook Join Table::Student ID ]
Set Variable [$ClassID ; value: Student Class Gradebook Join Table::Class Identification ]
Go to Layout [ “Student Class Attendance Participation Computation” (Student Class Attendance Participation Computation) ]
Set Field [Student Class Attendance Participation Computation::Student ID ; $StudentID ]
Set Field [Student Class Attendance Participation Computation::Class Identification ; $ClassID ]
Go to Layout [<original layout>]
Go to Record/Request/Page [next ; exit after last ]
1. A file (database) can have many tables.
2. The relationship graph can show:
a. Tables (& table alias’ -all called table occurrences) from the SAME database (file)
b. Tables (TOs) from other FM files/databases it can see thru a network. These are sources.
c. ODBC sources for approved SQL dbs. This is also called ESS (external SQL sources) with proper DNS (data named source) using the correct ODBC drivers. User permissions apply, of course!
3. You can SEE any table as on the relationship graph. You can interact with the data as if it resided in the same file as the graph (layouts, value lists, scripts, etcetera.) You can only DEFINE (modify) the fields at the source db.
Some developers use a “separation model” where the data is in separate dbs/tables from the interface file. As long as a connection allows a table source to be added to the graph, it seems almost as if it’s the same file! Note the caveats above.