My company saves 2010 excel workbooks in a shared network drive. The problem is that everyone has access to them so sometimes they are mistakenly deleted. Is there a way to protect the 2010 excel workbooks so that they can not be deleted from the shared network drive?

My company saves 2010 excel workbooks in a shared network drive. The
problem is that everyone has access to them so sometimes they are
mistakenly deleted. Is there a way to protect the 2010 excel
workbooks so that they can not be deleted from the shared network
drive?

Permissions???

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

In article , GS wrote:
My company saves 2010 excel workbooks in a shared network drive. The
problem is that everyone has access to them so sometimes they are
mistakenly deleted. Is there a way to protect the 2010 excel
workbooks so that they can not be deleted from the shared network
drive?

Permissions???

I see the classic "security vs access" dichotomy here. :)
I suspect that the OP's staff are needing write access to these files, which
really means they aren't secure anyway - someone could delete all the data
and save the file (for example). I suggest people keep their files secure on
their computer, and copy them to the shared drive regularly. Then you have a
'which file is the current one and how current is it' problem of course. :)
Or you could rely on regular and frequent backups of the whole disk ?

My understanding of shared drives is that permissions aren't easily settable
by file, and given write access, it's all kind of moot anyway. :)

Security or access remains the question. I don't think there's been a good
answer yet. :) :)

I agree in general, but I thought Active Directory availed more fine
control via Group Policy implementation.

Another option is to implement a repository where access/permissions
can be controlled in a more granular fashion. One example is PDM Works,
where users must login/logout files. What they're allowed to do with
the files can be controlled to a very fine-grained set of rules.

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

In article , GS wrote:
I agree in general, but I thought Active Directory availed more fine
control via Group Policy implementation.

Another option is to implement a repository where access/permissions
can be controlled in a more granular fashion. One example is PDM Works,
where users must login/logout files. What they're allowed to do with
the files can be controlled to a very fine-grained set of rules.

... so is that a product you have to buy form a non MS supplier ?
Seems crazy to me that the MS system doesn't come with an easy way to set
permissions ... but there you go. :)

In article , GS wrote:
I agree in general, but I thought Active Directory availed more fine
control via Group Policy implementation.

Another option is to implement a repository where access/permissions
can be controlled in a more granular fashion. One example is PDM
Works, where users must login/logout files. What they're allowed to
do with the files can be controlled to a very fine-grained set of
rules.

.. so is that a product you have to buy form a non MS supplier ?
Seems crazy to me that the MS system doesn't come with an easy way to
set permissions ... but there you go. :)

PDM Works is 3rd party software that I use with my CAD apps for
controlling who has what access/permissions to work with files in the
repository. It utilizes NTFS permissions along with its own methodology
of files/users management.

Otherwise, I suspect ActiveDirectory+GroupPolicy would be able to
govern what users can do to a finer degree.

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion