I hate to repeat myself, but it seems the problem with object notation is that it's not as straightforward to know if a field has been changed or not.
perhaps until now, we have been thinking of simply code like [myTable]myField.prop:="123" and it seems crazy that 4D doesn't understand that the field has been updated. but that's not how references work. for example, imagine a method that does this: // myMethod C_OBJECT($0) $0:=[myTable]myField it is possible to do something like this: myMethod.prop:="abc" there is literally no way of knowing that an object is a field, just by parsing the code. > 2017/11/01 11:14、David Adams via 4D_Tech <4d_tech@lists.4d.com> のメール： > If changing a field and then saving the record doesn't save the field change, > that's a bug. ********************************************************************** 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:4d_tech-unsubscr...@lists.4d.com **********************************************************************
