On Apr 30, 6:50*am, CellShocked
<cellshoc...@thecellvalueattheendofthespreadsheet. org wrote:
On Wed, 27 Apr 2011 09:13:01 -0700 (PDT), Schatzi

wrote:
That is a great idea. How do I use macros to unhide a workbook?
This way, if they initially save a copy to their own drive, it will be
more difficult for them to hack it, but not impossible. Hopefully they
will be less likely to try and save it immediately when they see that
nothing is available.

* If you have workers that sit and hack spreadsheets instead of what they
are supposed to be doing, and you do not notice that they did not get
what they were supposed to get done DONE, then you either do not assign
them enough work, or do not hold them to the timelines of the work you
give them, or do not police them well enough to insure that they are
working on said assignments, instead of attempting to hack company
spreadsheets.

* I would simply make a policy that states that if they are modifying
workbooks specifically meant to be used as is, they are committing acts
other than their JOB DUTIES and are subject to disciplinary action.

* If work assignment levels are so lax that they have enough time to
perform such illicit hacking behaviors, then again, it is YOU that is not
giving them enough assignments to be sure they stay busy.

* No work? *Have them polish up their duties, or think of things yourself
for them to polish up to improve operations or the company image in some
way.

* It shouldn't be hard to weed out the freeloaders and those with ill
intent.

I am not worried in quite the way you are thinking. First, the workers
are not directly under me. Second, the concern is that they might
leave the company and take the program with them. While part of the
company, they can use it to their heart's content, so there would be
no need to hack the program. If they took the program with them, then
there would be an issue.