Hi Dr. Hawkins, If you just want to prevent overwriting of older files, why don’t you just use a new name for the file. You can always track which file is the newest in a few different ways.
For Example: File1, File2, or append a date and time to the file name. At the end of some larger time period you can decide which ones to keep and which to toss out. You don’t have to screw around with file permissions at all then. You can always check for the existence of a file too by name. If the file already exists then you know not to rewrite it. Create a new name for a new file and use that one instead. Still if LC is not doing what it is supposed to, or doing something that it shouldn’t do, it should be fixed. Good luck, Rick > On Dec 1, 2016, at 2:53 PM, Dr. Hawkins <doch...@gmail.com> wrote: > > On Thu, Dec 1, 2016 at 11:32 AM, Dr. Hawkins <doch...@gmail.com> wrote: > >> I'm trying to put in a failsafe that prevents overwriting older files. Do >> I need to change the owner of the files for this??? >> > > That doesn't do it either: > > get shell ("chmod -w " & oldFlDir && "; chown dhArchive " & oldFlDir) > > > gets > > chown: /Users/hawk/Documents/dhbk/16/1611/161130: Operation not permitted > > And I still own the directory, and it's still write-enabled. > > -- > Dr. Richard E. Hawkins, Esq. > (702) 508-8462 > _______________________________________________ > use-livecode mailing list > firstname.lastname@example.org > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list email@example.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode