Bob, To throw in my $0.02 - why not ditch the output form and display the records in a listbox? I use arrays but I know a lot of people like selection based ones. I prefer arrays, especially if I want to limit the user's ability to lock a record. You really can't do that if it's displayed in an array.
A listbox eliminates most of the issues you describe. You would simply catch the double click in the listbox and then you evaluate the user's credentials before even looking for the record. If they have no read write permissions don't even put the table into read write. If they have permission unlock the table, query the record, set the input form (may not need to) and call modify record. Or you might have a different form for only viewing vs. editing. If you use a selection based listbox there are more record locking, table r/w issues to deal with but the principle is more or less the same. That's another reason I prefer arrays for lists like this. Plus you have the option of throwing the edited record into a separate process just for that purpose which allows users to have multiple records open at one time. Important in my world but not everywhere. On Fri, Aug 19, 2016 at 12:35 PM, <[email protected]> wrote: > What I want is that when I open the form that uses only non-enterable > fields, NOT to lock the record. Since I'm in Modify Selection, though, by > default everything is in a read-write state. Hence, when a user opens a > "non-enterable" record, it still is locked to other users. > > Is there a way to accomplish this, other than to open the "non-enterable" > record in a new process? > -- Kirk Brooks San Francisco, CA ======================= ********************************************************************** 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] **********************************************************************
