You missed my point on your point ;-) You can offer all of that without giving the user access to that in case you DON’T want them to have it. For example, you could create a set via a query, then give your users access to ONLY query the selection, or whatever. You don’t need that new 4D weird editor to do that.
In a complex application it is normal to have to do a little extra coding. For example, we have a multi-company accounting system. When a user connects to one company we want to shield him from inadvertently access data from another company. So no matter what query he does, we will narrow the selection programmatically to exclude data we don’t want displayed. The nice thing about Miyako’s component is you can customize it to do these types of things, whereas 4D’s new query editor doesn’t leave you any choice. Cheers, Paul > Le 7 mars 2017 à 16:59, Charles Miller via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > You missed my point. Let's say I have a db where users can only see only > certain regions of data. So You code that when you launch the process for > them, their all records actually shows a subset. In the old quest editor if > you had a command query selection that is all the user could do. In the new > query editor, the user can switch to create a new selection, into a set etc. > > Thus you as a developer must add extra code every time they do a query, > where in previous versions you did not > > Regards > > Chuck ********************************************************************** 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 **********************************************************************
