maybe a method called before the user prints is doing something like: Read only([table]) print routine
Chip > Thank you so much, Chuck! Changing the order of the commands did the > trick! I will be sure to remember this next time. > > My server process does not end, but I am not using any print jobs on > it, and, oddly, normal users use the exact same printing code in > processes that do not end for a long time and do not end up locking > the file with the report formats, either. So, still offbeat behavior, > but I can live with it. > > JJ > >> OnWed, 11 Mar 2020 14:06:30 -0400, Chuck Miller >> <cjmil...@informed-solutions.com >> <mailto:cjmil...@informed-solutions.com>> wrote: >> >> Remember you must have code in the following sequence >> >> Unload record >> read only >> >> The reason it may be unlocking on server is that the process ends >> > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ********************************************************************** ------------ Hell is other people Jean-Paul Sartre ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
