hiding a file
 

i want to block anyone from opening an excel file without a password. or
maybe the folder it's in, if that's more feasible.

Thanks in advance for your help.

Hi
in the File - Saveas dialog of Excel specify (in the Tools menu) a password
for reading this file

--
Regards
Frank Kabel
Frankfurt, Germany
"lpeterson" schrieb im Newsbeitrag
...
i want to block anyone from opening an excel file without a password. or
maybe the folder it's in, if that's more feasible.

Thanks in advance for your help.

I would go with Frank's suggestion of passwording the file although there are
password crackers out there freely available on the 'net so if your data is
extremely sensitive you may re-think this.

If using WindowsXP...........

You can set permissions to restrict access to particular folders.

HOW TO: Set, View, Change, or Remove Special Permissions for Files and
Folders in Windows XP
http://support.microsoft.com/kb/308419


Gord Dibben Excel MVP

On Wed, 29 Dec 2004 09:37:04 -0800, lpeterson
wrote:

i want to block anyone from opening an excel file without a password. or
maybe the folder it's in, if that's more feasible.

Thanks in advance for your help.

Gord Dibben wrote...
I would go with Frank's suggestion of passwording the file although
there are
password crackers out there freely available on the 'net so if your
data is
extremely sensitive you may re-think this.

FileOpen passwords are MUCH stronger than internal passwords.

If using WindowsXP...........
....

Why limit yourself to WinXP? All the NT variants (NT4, NT5.0 aka 2000,
NT5.1 aka XP) provide permissions on NTFS drives, but no version of
Windows provides any security on FAT file systems. For that matter,
Windows 95/98/Me clients connected to Windows NT/2K/XP/2003 file
servers may be able to set permissions on file server drives (dunno,
never worked where such a configuration was used).

Now restricting access to shared folders implies the person desiring to
do so himself/herself has the necessary permissions to modify
permissions for files and/or folders on shared drives. On
well-administered Windows file servers that's seldom if ever the case.
Nevertheless, the OP may be able to do this (most Windows file servers
are NOT well-administered, but most Windows users are ignorant or the
existence of permissions, so seldom screw them up).

Thanks for these nuggets Harlan.

You probably noticed I also forgot to include the possibilities of moon phases
and whether or not the OP resided above or below the Tropic of Capricorn.

Gord

On 29 Dec 2004 12:54:29 -0800, wrote:

Gord Dibben wrote...
I would go with Frank's suggestion of passwording the file although
there are
password crackers out there freely available on the 'net so if your
data is
extremely sensitive you may re-think this.

FileOpen passwords are MUCH stronger than internal passwords.

If using WindowsXP...........
...

Why limit yourself to WinXP? All the NT variants (NT4, NT5.0 aka 2000,
NT5.1 aka XP) provide permissions on NTFS drives, but no version of
Windows provides any security on FAT file systems. For that matter,
Windows 95/98/Me clients connected to Windows NT/2K/XP/2003 file
servers may be able to set permissions on file server drives (dunno,
never worked where such a configuration was used).

Now restricting access to shared folders implies the person desiring to
do so himself/herself has the necessary permissions to modify
permissions for files and/or folders on shared drives. On
well-administered Windows file servers that's seldom if ever the case.
Nevertheless, the OP may be able to do this (most Windows file servers
are NOT well-administered, but most Windows users are ignorant or the
existence of permissions, so seldom screw them up).

Hey Gord,
You'd think that he'd be all "typed out", answering that aaron_kempf jerk in
the WHY thread of the excel group, but it just probably whetted his
appetite!<bg
--


Regards,

RD
--------------------------------------------------------------------
Please keep all correspondence within the Group, so all may benefit!
-------------------------------------------------------------------

"Gord Dibben" <gorddibbATshawDOTca wrote in message
...
Thanks for these nuggets Harlan.

You probably noticed I also forgot to include the possibilities of moon
phases
and whether or not the OP resided above or below the Tropic of Capricorn.

Gord

On 29 Dec 2004 12:54:29 -0800, wrote:

Gord Dibben wrote...
I would go with Frank's suggestion of passwording the file although
there are
password crackers out there freely available on the 'net so if your
data is
extremely sensitive you may re-think this.

FileOpen passwords are MUCH stronger than internal passwords.

If using WindowsXP...........
...

Why limit yourself to WinXP? All the NT variants (NT4, NT5.0 aka 2000,
NT5.1 aka XP) provide permissions on NTFS drives, but no version of
Windows provides any security on FAT file systems. For that matter,
Windows 95/98/Me clients connected to Windows NT/2K/XP/2003 file
servers may be able to set permissions on file server drives (dunno,
never worked where such a configuration was used).

Now restricting access to shared folders implies the person desiring to
do so himself/herself has the necessary permissions to modify
permissions for files and/or folders on shared drives. On
well-administered Windows file servers that's seldom if ever the case.
Nevertheless, the OP may be able to do this (most Windows file servers
are NOT well-administered, but most Windows users are ignorant or the
existence of permissions, so seldom screw them up).

Gord Dibben wrote...
Thanks for these nuggets Harlan.

You probably noticed I also forgot to include the possibilities of
moon phases
and whether or not the OP resided above or below the Tropic of
Capricorn.

Hiding your ignorance of basic system administration behind snideness?

To repeat, all NT-based versions of Windows set permissions, not just
XP. Don't you think, just perhaps, your XP comment might lead some
readers to assume this was only available in XP?

Changing file or directory permissions in turn requires that the person
trying to do so has either Change Permissions or Take Ownership
permissions or 'owns' the file or directory. That's not spelled out in
the nice KB article you linked.

Finally, file permissions are dangerous things. It's not that difficult
for a user to screw up their own access to files or directories. This
is about as dangerous as providing advice to edit the Registry. It
should come with a warning (and would if the advice were given by
someone who knows what he's doing, which doesn't seem to include you).