Moving backend to secure folder

[Trish]

I have an Access 2003 database application consisting of a frontend on
each user's desktop and a backend on a network drive. I have been
asked to move the backend into a folder that the users can't actually
see from Windows Explorer - a folder for which only a few of us have
privileges. The fear is that someone will accidentally delete or
damage the file. Is this possible or do we need to simply give
everyone read/write privileges, but not delete capability? Many
thanks for your help.

Trish

[Granny Spitz via AccessMonster.com]

Trish wrote:

I have been
asked to move the backend into a folder that the users can't actually
see from Windows Explorer - a folder for which only a few of us have
privileges.

Only the users who have permissions on that folder will be able to open the
database.

Is this possible or do we need to simply give
everyone read/write privileges, but not delete capability?

If it's a multiuser database, every database user should have
read/write/create/delete permissions on the folder. Any less and some of the
users will be blocked from opening the database.

--
Message posted via AccessMonster.c om
http://www.accessmonster.com/Uwe/For...ccess/200610/1

[Trish]

Granny Spitz via AccessMonster.c om wrote:

Trish wrote:

I have been
asked to move the backend into a folder that the users can't actually
see from Windows Explorer - a folder for which only a few of us have
privileges.

Only the users who have permissions on that folder will be able to open the
database.

Is this possible or do we need to simply give
everyone read/write privileges, but not delete capability?

If it's a multiuser database, every database user should have
read/write/create/delete permissions on the folder. Any less and some of the
users will be blocked from opening the database.

--
Message posted via AccessMonster.c om
http://www.accessmonster.com/Uwe/For...ccess/200610/1

How do you keep people from deleting the file altogether?

[Trish]

Granny Spitz via AccessMonster.c om wrote:

Trish wrote:

I have been
asked to move the backend into a folder that the users can't actually
see from Windows Explorer - a folder for which only a few of us have
privileges.

Only the users who have permissions on that folder will be able to open the
database.

Is this possible or do we need to simply give
everyone read/write privileges, but not delete capability?

If it's a multiuser database, every database user should have
read/write/create/delete permissions on the folder. Any less and some of the
users will be blocked from opening the database.

--
Message posted via AccessMonster.c om
http://www.accessmonster.com/Uwe/For...ccess/200610/1

How do you keep people from deleting the file altogether?

[Granny Spitz via AccessMonster.com]

Trish wrote:

How do you keep people from deleting the file altogether?

Take away the box of Krispy Kremes and say "No more for you," and restore the
database from last night's backup. (Or you can tell them they'll be fired if
they delete the database, but that's not as effective a punishment.)

--
Message posted via AccessMonster.c om
http://www.accessmonster.com/Uwe/For...ccess/200610/1

[David W. Fenton]

"Granny Spitz via AccessMonster.c om" <u26473@uwewrot e in
news:689a769bd7 0e4@uwe:

If it's a multiuser database, every database user should have
read/write/create/delete permissions on the folder. Any less and
some of the users will be blocked from opening the database.

This is simply not true.

The users need READ/CHANGE permission. They don't need DELETE. The
result of that is that the LDB file will not be deleted when users
without DELETE permission exit the database, but as long as some of
the administrative users have that permission, it's OK. I have had
many clients who run with users having no DELETE permissions on the
folder where their back end data file is stored.

Another approach is to deny DELETE on the back end file itself.
However, after a compact, you'd have to restore those permissions,
since it's actually a new file. I'm sure there's an API for setting
permissions, so perhaps one could set up an Access compact that
would restore the DELETE deny setting to the compacted file.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Larry Linson]

"Granny Spitz via AccessMonster.c om" <u26473@uwewrot e in message
news:689aaf6c20 e96@uwe...

Trish wrote:

>How do you keep people from deleting the file altogether?

Take away the box of Krispy Kremes and say "No more for you," and restore
the
database from last night's backup. (Or you can tell them they'll be fired
if
they delete the database, but that's not as effective a punishment.)

The "official" way to state that is: "Not deleting the database is a
condition of continued employment." But, if you get an employee who's
really ticked off, that's not a deterrent.

:-)

Larry

[Trish]

LOL

I think I will quote you verbatim if my manager asks what I found out.

Thanks so much for your help.

Trish

[Granny Spitz via AccessMonster.com]

David W. Fenton wrote:

>If it's a multiuser database, every database user should have
read/write/create/delete permissions on the folder. Any less and
some of the users will be blocked from opening the database.

This is simply not true.

The users need READ/CHANGE permission. They don't need DELETE. The
result of that is that the LDB file will not be deleted when users
without DELETE permission exit the database, but as long as some of
the administrative users have that permission, it's OK. I have had
many clients who run with users having no DELETE permissions on the
folder where their back end data file is stored.

And the sky parted the tall cumulonimbus clouds, and a thunderous voice said,

"Thou hast proof my son David hast lifted thy plonk, ... so don't screw it up
again!"

[Granny Spitz via AccessMonster.com]

David W. Fenton wrote:

>If it's a multiuser database, every database user should have
read/write/create/delete permissions on the folder. Any less and
some of the users will be blocked from opening the database.

This is simply not true.

The users need READ/CHANGE permission. They don't need DELETE. The
result of that is that the LDB file will not be deleted when users
without DELETE permission exit the database, but as long as some of
the administrative users have that permission, it's OK. I have had
many clients who run with users having no DELETE permissions on the
folder where their back end data file is stored.

And the sky parted the tall cumulonimbus clouds, and a thunderous voice said,

"Thou hast proof my son David hast lifted thy plonk, ... so don't screw it up
again!"

>:
.
:

... so I was sitting there eating my jelly filled Krispy Kreme, two of my
coworkers were chatting on the phone to their boyfriends, and three of the
young men were playing Nerf basketball in the cube and roared "SCORE!" The
boss walked in and looked around with a confused look on his face. "Why
aren't you people working?" He turned to me and asked "Why aren't you
telling these people to get back to work?" I answered "My mouf iff toof
fuwell," and one of my coworkers answered "We can't work. We're locked out
of the database because no one here today has admin privs to delete the LDB
file when the database crashed."

--
Message posted via AccessMonster.c om
http://www.accessmonster.com/Uwe/For...ccess/200610/1