I am running into an annoying bug with "Execute on client" functions. Even though I have put UNLOAD RECORD and READ ONLY commands into the methods that are executed there, the client process keeps records locked even if they are unloaded and set to read only. I am noticing this as I try to test new reports to print on a client that are saved into a report table. Consequently, I cannot tweak the report that I am using for printing because every report printed as a result of an "Execute on client" command locks that report permanently until I close the client machine. This is wasting a ton of my time. "Execute on server" will unload the records and does not seem to be doing this sort of unpredictable and unavoidable locking.
JJ ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
