> On Jan 16, 2017, at 6:20 AM, Chip Scheide <[email protected]> wrote: > > … > ... > > … > ... > > 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.
Thanks for your reply, Chip. Given my experience with v12, I would agree that something internal is different. While I take your point about the possible dangers of automatic relations, I think the threshold necessary for manual relations is somewhere greater on a complexity continuum, which, the db in my charge has not nor is ever likely to exceed while I’m the developer. These are one-step removed Many or One links in all cases. And while it would have been technically appealing twenty-plus years ago to start from scratch with manual, I think a justifiable consideration exists, in this case, for factoring in the possibility of future developers. What I mean is, given the size, relative simplicity and one-developer public-sector nature (educational setting) of this db, I considered it prudent to develop with a KISS mindset, in case someone had to take over unexpectedly. This smallish db is emblematic of why 4D still features automatic relations. Had things been otherwise... had i had requirements for such relational dependancies, with possible circular reference implications, then the need for manual would have been unavoidable… assuredly so, if or because circular reference problems had cropped up during design or modification. But that was not the case. Secondarily, given as I described below, that related content updates correctly, if I willy-nilly activate a different form object… without a load event or directly related object method activation... it seems an indication of something other than a circular reference. To be sure I will again be tracing and searching the db, tomorrow, one more time, before I implement a tab-control object method, which, Tim and Keith indicated v15 naturally expects. Hopefully I didn’t misrepresent or misunderstand your points. In any event, thanks very much for your detailed reply and time. max > … > ... > > 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] > ********************************************************************** ********************************************************************** 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] **********************************************************************
