I read the documentation, and that is why I do what I do, I was just trying to note it for the list.
However, being able to delete from a selection created after a READ ONLY(*) command is not according to the documentation, but it “works” for me in practice. I find it handy, but counter to expectations. I prevent that from happening in my application for the regular user. Anyway, a little off of the original topic. JJ > On Dec 6, 2017, at 3:15 AM, [email protected] wrote: > > > Message: 6 > Date: Wed, 6 Dec 2017 05:25:27 +0000 > From: Keisuke Miyako <[email protected] <mailto:[email protected]>> > To: 4D iNug Technical <[email protected] <mailto:[email protected]>> > Subject: Re: Execute on server gotcha > Message-ID: <[email protected] > <mailto:[email protected]>> > Content-Type: text/plain; charset="utf-8" > > READ ONLY is a declaration that applies to subsequent operations. > > I think that is pretty clear from the documentation. > > http://doc.4d.com/4Dv15/4D/15.5/READ-ONLY.301-3577015.en.html > <http://doc.4d.com/4Dv15/4D/15.5/READ-ONLY.301-3577015.en.html> > > quote: > > READ ONLY changes the state of aTable to read-only for the process in which > it is called. All subsequent records that are loaded are locked, and you > cannot make any changes made to them. If the optional * parameter is > specified, all tables are changed to read-only state. ********************************************************************** 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] **********************************************************************
