Prevent distribution of file

  • Thread starter Thread starter daniel.j.morton
  • Start date Start date
D

daniel.j.morton

Hello

I have an excel file which is placed on an NT server where people read
and write to it to complete a company budget. I want to prevent people
from making copies of the file to save to local drive or send the file.
Any suggestions? It does not need to be 100% fullproof but a good level
of prevention would be good. Perhaps this is not specifically an excel
question but NT server side? I am not sure.

thank you.

Daniel
 
(e-mail address removed) shared this with us in microsoft.public.excel:
Hello

I have an excel file which is placed on an NT server where people read
and write to it to complete a company budget. I want to prevent people
from making copies of the file to save to local drive or send the
file. Any suggestions? It does not need to be 100% fullproof but a
good level of prevention would be good. Perhaps this is not
specifically an excel question but NT server side? I am not sure.

thank you.

Daniel
Click to expand...

It is not possible. If people can read a file, they can copy it, print
it, send it. Period.
You cannot solve this with technology. Write (and enforce) a policy for
things like this.

--
Amedee Van Gasse using XanaNews 1.17.3.1
If it has an "X" in the name, it must be Linux?

How To Ask Questions The Smart Way

How to Report Bugs Effectively
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
Only ask questions with yes/no answers if you want "yes" or "no" as the
answer.
http://homepages.tesco.net/~J.deBoynePollard/FGA/questions-with-yes-or-n
o-answers.html
 
One thing that's not too secure...

Make your workbook require that you use macros--maybe some sort of user defined
function that will break the functionality if macros are disabled and that UDF
can't recalculate. Then have a macro (or a few macros) check the path of the
workbook--if it's not the correct spot, do something that makes the workbook
difficult to use.

But all this depends on macro security and macro security can be broken pretty
easily.

And this doesn't stop the saving or sending--it just tries to stop any copy from
working correctly.
 
Back
Top