Although I use object extensively in code, I don’t use them in very many fields. I do have several “settings” fields and find object type fields very useful here. Being able to add settings in the future without changing the structure is great and it seems like less work to have an extensive, but organized list of settings in an object than other methods I’ve tried in the past.
The only other object type field I use is one for tracking the breed of an cow. Each cow can be composed of 0..n breeds, each with a percentage of the total. This could have been in another table, but in this case it worked very nicely to put this information into an object field for each animal. I guess the bulk of the data I work with in current projects tends to be pretty structured, so regular fields work best. I worked on a project many years ago where object fields would have been perfect. The users could create their own “fields”. Lots of them. I think Pat Bensky does something like that, doesn’t she? Anyway, that’s all I do with them. -- Cannon.Smith Synergy Farm Solutions Inc. Hill Spring, AB Canada 403-626-3236 <can...@synergyfarmsolutions.com> <www.synergyfarmsolutions.com> > On Jul 14, 2017, at 4:15 PM, David Adams via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > More thoughts and comments wanted! It would be helpful to everyone to hear > real-world stories about how you're finding object fields helpful. ********************************************************************** 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 **********************************************************************
