While I can not speak to v15 specifically, generally, automatic relations can be problematic, while not for the reason(s) you are questioning. The biggest problems are: - circular relations - relational path
Circular relations - given tables A, B, C and D, and the below relationships A -> B -> C -> D -> A B -> D -> A load a record in table A, with automatic relations - what happens? - you can lose your loaded record in table A as auto relations chain from A to B to C to D back to A. - You can lose your loaded record in table A as auto relations chain from A to B to D to A - you don't get the selection in table C as expected because of the relational chain A to B to D As to specifically what you are seeing, it is likely due to some change inside 4D, probably as part network traffic reduction, in when auto relations get triggered. Solution(s) - Use RELATE ONE, RELATE MANY, RELATE ONE SELECTION, RELATE MANY SELECTION to trigger your updates. - make your relations manual, and trigger them as needed to avoid the issues I mention above. On Fri, 13 Jan 2017 13:48:41 -0900, Max Morrison wrote: > > Many-table records displayed in a subform are not automatically > updating after record-change button click (next, previous, etc). The > relations are automatic for simplicity. The subform operated as > expected under v12. Oddly… after the next-record button click and > record data changes but subform data does not, if I activate a > different data object or click on a different tab of a tab control, > the many-records subform data updates. Object methods contain nothing > related to records, and, tracing shows nothing significant to > generate the update of the subform. > > I feel like I’m missing something obvious but I can't grok it so > far... I’ve read everything pertinent (I think) from versions 13 to > 15 and can not find anything that indicates functionality of subforms > or relations or input forms have changed, such that, an input-form > record-change-click no longer automatically updates related > many-table records in a subform. I’ve re-instantiated the subform > but no luck. This happens on a number of tables, many-to-one as well, > multi-tab-controlled subforms too. > ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
