as a general rule, if objects are meant to share a common structure, the choice should be to use a record, not a single object field.
the closest thing we have to a "class" in 4D is a table, not an object. http://doc.4d.com/4Dv17/4D/17/Dataclasses.300-3777698.en.html 2018/10/04 23:24、Chip Scheide via 4D_Tech <[email protected]<mailto:[email protected]>>のメール: 3 - You could run a method at shutdown (during development) which would document/comment every object field. This information (object.content) could be put into the table's object field(s) comment(s), and/or into a separate comment only method outlining the structure of every object field. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
