![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
This problem involves 3 files with tables: System System Teachers Teachers Contracts Appointments One table in file 'System' has a field 'WorkingYear' A field in table 'Teachers' calculates a copy of System::Workingyear A TO for 'Teachers' in a file 'Contracts' uses 3 fields to get acces via a relation to a table 'Appointments'. One of these fields is the calculated field with a copy of 'System::WorkingYear' A layout for 'Teachers' in this file 'Contracts' contains a portal for 'Appointments' When the System::WorkingYear field is changed, the copy in the Teachers file is updated accordingly, but the relation to Appointments is not updated. All the calculation fields are unstored. What rule in the FM documentation did I miss? So I am looking to related records by a set of 3 values, one of these is a calculated field. Changing the target of the calculated field does not update the set of related records. |
#3
| |||
| |||
|
|
This problem involves 3 files with tables: System System Teachers Teachers Contracts Appointments One table in file 'System' has a field 'WorkingYear' A field in table 'Teachers' calculates a copy of System::Workingyear A TO for 'Teachers' in a file 'Contracts' uses 3 fields to get acces via a relation to a table 'Appointments'. One of these fields is the calculated field with a copy of 'System::WorkingYear' A layout for 'Teachers' in this file 'Contracts' contains a portal for 'Appointments' When the System::WorkingYear field is changed, the copy in the Teachers file is updated accordingly, but the relation to Appointments is not updated. All the calculation fields are unstored. What rule in the FM documentation did I miss? So I am looking to related records by a set of 3 values, one of these is a calculated field. Changing the target of the calculated field does not update the set of related records. |
)
#4
| |||
| |||
|
#5
| |||
| |||
|
#6
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |