yea, the problem with zip files with passwords is u can still open the file, just cant extract anything. but yea, a zip file with a password works well. it makes a huge difference if u have active directory or not, so find out.

I guess you have a point, and I forget that you can still delete it so it doesn't solve all the problems.

http://en.wikipedia.org/wiki/Linux" onclick="window.open(this.href);return false;

But seriously, it'll be interesting to see how you will allow users to write to a folder (to add files) but not allow them to delete the files in the folder.

In Linux, I've seen this done using two directories, one has public write access (where you upload) and one does not (where you download). Then you have some script or ftp hook that moves uploaded files from the upload directory to the download directory and applies the correct permissions.

You might be also able to use a single directory with public write access and have some script or ftp hook that changes the permissions of the files in the directory but not the containing folder. But a quick test shows that although I was not able to edit the files in the directory, I was able to just straight delete the entire thing. So I'm not so sure about that approach.

In either case, you need an active script / cron job or an FTP hook to change permissions.

what we're gonna do is this: keep a shared folder locally on a users machine, not on the network. This way, we can set permissions how we want them (as stated previously), and only that machine's user can delete or replace files. When a file needs to be deleted or replaced, it'll be done on his machine.

thanks for all the suggestions, though

i know about the advanced permissions. but changing them for the "Everyone" group, that means nobody can delete or replace files. Nobody. Unless the permissions are changed back. (this is in regards to a folder on the network)

We decided that the shared folder on the local machine, with the permissions set as such is the best way to go about it.