We use adobe file to store information that several users have access to. The challenge is we need to update the files that multiple people have access to and need the group that updates them to be able to save even if another user is already in the file. Basically, we need a group to be read only and another group to be able to update while the read only group is in the file. We use 9.0. Thanks.
Brian
You will want to discuss this with whomever is the server admin.
I had a similar question when a PDF library I maintain was hosted in a Novell network
and when it was migrated to an Active Directory network.
I've the recollection that permissions profiles for individuals/groups do not extend to the file level.
In both networks, any tag line by an application will preclude overwrite, save of edits, or deletion of the file(s).
Some approaches:
Coordinate with IT/Server admin to "turn off" user accessed shares or servers at designated times.
Perform the updates then via the "back office".
Logistical coordination may be a challenge.
More so for larger organizations.
Maintain a staging zone that is a clone of production.
Update it. Copy "top level" directories with different names than the equivalent production zone "top levels" These hold the new content (and likely unchanged "old" content).
Drop in an "entry" PDF above which points the to content through the new "top directory" name.
Delete all "old" under the applicable "top directory". Any PDF that is "hooked" by any application remains.
In Novell you can rename an old "top directory" and, if desired, move it to further isolate it (helps to break the path used by programmatic "hooks").
In Active Directories nothing in the path to a "hooked" file can be renamed, moved or deleted.
(Well maybe an IT server OS admin can but mere muggles cannot.) So, in AD, you check periodically & try to flush the file(s)/folder(s).It is likely that there are slicker tricks.
But, often, such call for skill sets and availability of those having them.
Oft times these prerequisites cannot be met for one reason or an other.
So, plug 'n chug is sometimes the least resource intensive and cost-effective method.
With that said, you could go to a content management approach.
May not get all the juice that is available with network based interactive PDFs and tiered Catalog indices.
However, parking new stuff is a breeze.
Good for you but, maybe, not good for end-users.
Then there is paper, binders, bookshelves, and file cabinets. Think of the new employment opportunities.Be well...
Be well...