On Sep 12, 2017, at 5:49 PM, Jeffrey Kain wrote: > Yeah, so many caveats to object fields. Bite the bullet, use a related > table...
Remember 4D’s implementation strategy for new features: - You get a little bit at a time. - The feature set is not complete. - The public (i.e. 4D developers) are not provided with any information about what the completed feature set will ultimately look like. It’s quite possible 4D Engineering doesn’t even know what the full feature set of object fields will be. Could be they just keep adding features based on what developers say we need, or maybe what 4D Engineering “thinks” a developer might need or find useful. Add to this the fact that 4D Engineers are not, and have never been, 4D developers. They don’t really use the thing that they are creating. Don’t get me wrong, I know 4D Inc. uses 4D internally for a lot of things. So 4D Inc. does eat their own dog food. But the guys in the kitchen making the dog food never really taste it. They cook it and then send it off for others to eat and wait to hear how good it tastes. And if it need more salt. Or if it is too spicy. You know what I’m saying. Tim ******************************************** Tim Nevels Innovative Solutions 785-749-3444 [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] **********************************************************************
