RE: Access database placed in a state...
- From: "David W. Fenton" <XXXusenet@xxxxxxxxxxxxxxxxxxx>
- Date: 29 Jan 2009 20:38:14 GMT
=?Utf-8?B?R29sZmlucmF5?= <Golfinray@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in news:D457792F-01F1-4003-9F26-C83D27445EC3@xxxxxxxxxxxxx:
Secondly, the backend file AND the folder it resides in must have
read/write/edit/ and delete rights for each user.
Technically, the back end folder does not require delete rights --
it will run just fine without it, though the LDB file will never be
deleted. The usual reason for doing this is to prevent users from
accidentally deleting your back-end data file. The minor downside is
that the LDB file won't be deleted when the last user exits your
app. This is only a problem if the LDB file gets corrupted, and in
that case, someone with delete permissions can take care of it.
My usual practice when I removed delete permissions was to have
regulars users without delete permissions and a few administrative
users *with* delete permissions (the couple of people who did
database maintenance). This has worked fine for years in several
installations I've had.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.
- References:
- Access database placed in a state...
- From: SimpleUser
- RE: Access database placed in a state...
- From: Golfinray
- Access database placed in a state...
- Prev by Date: RE: Volunteer Scheduling
- Next by Date: Validation Rules
- Previous by thread: RE: Access database placed in a state...
- Next by thread: Need help with my database
- Index(es):
Relevant Pages
|