multiple users' simultaneous access to a MS Access database

#31

Tony Toews <ttoews (AT) telusplanet (DOT) net> wrote in
news:mthqa6tps3lvg1jvr8g5cnpvj2tr1i43fv (AT) 4ax (DOT) com:

Quote:

On 6 Oct 2010 20:11:05 GMT, "David-W-Fenton"
NoEmail (AT) SeeSignature (DOT) invalid> wrote:

Certainly if as with NTFS you can set permissions only on
existing files and folders,

Actually you can set permissions on folders and possibly files
that don't exist using ACL and Active Directory and such. I
forget the details as it's been quite a while now but I wrote a
program for a construction company to set permissions on job
subfolders, such as Drawings, Invoicing, TimeSheets to be by
Active Directory group.

I'm interested in the idea of setting permissions on files that
don't yet exist, as distinct from the usual thing I've done of
removing DELETE permissons on the folder (that propagates to the
files created inside it, of course).

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

#32

On Oct 5, 3:53*pm, "Bob Barrows" <reb01... (AT) NOyahoo (DOT) SPAMcom> wrote:

Quote:

James A. Fortune wrote:
On Oct 4, 1:33 pm, "Bob Barrows" <reb01... (AT) NOyahoo (DOT) SPAMcom> wrote:
James A. Fortune wrote:
On Oct 4, 7:51 am, "Bob Barrows" <reb01... (AT) NOSPAMyahoo (DOT) com> wrote:
James A. Fortune wrote:
On Sep 30, 10:53 am, The Frog <mr.frog.to.... (AT) googlemail (DOT) com
wrote:
This might seem like a silly question, and maybe I just missed
the wording somewhere, but I thought it prudent to ask:
Is the database application split into Front End / Back End or is
it just a 'stand-alone' file (.mdb)?

What part of "back end databases" or "front end databases linked
to those tables" was unclear :-)?

Only the part about who said those words ... care to point out that
post to us?

I posted those words. The portions in double quotes were direct
quotations. Didn't my post of Sep 29 -- the one The Frog replied to
-- show up? I still see it with Google Groups.

Are you the OP (original poster)? If not, then you really can't speak
for the OP can you? We're still trying to make suggestions to solve
zufie's issue.

I was replying to a comment by David Fenton. *I didn't realize that
The Frog was asking the OP a question because that post was a reply to
my post. *I have to confess that I haven't tried very hard to solve
zufie's issue, nor have I even read the thread carefully enough to
know what the issue is in detail, much less solve it.

Ah, *I thought Frog's question was obviously directed to the OP despite
it being a reply to your post, and you thought it was directed to you
despite it being a non sequitur from your post. :-) All is clear now.
Thx, and apologies.

--
HTH,
Bob Barrows

Yes. It's all about me :-). Sometimes it's hard to tell the
erroneous non sequiturs from the intentional ones :-).

James A. Fortune
CDMAPoster (AT) FortuneJames (DOT) com

#33

On Oct 6, 9:11*pm, "David-W-Fenton" <NoEm... (AT) SeeSignature (DOT) invalid>
wrote:

Quote:

On Novell, can you set permissions by file type? If not, then I
don't understand what you mean about setting LDB permissions. Also,
I don't know why you'd set "Delete Inhibit" on the LDB. I don't know
what that means, but it seems to imply that it prevents the deletion
of the LDB, which is not necessarily a preferred environment to run
in. Certainly if as with NTFS you can set permissions only on
existing files and folders, removing DELETE permission can be a
safety measure (preventing a user from "accidentally" deleting your
back end), but you were speaking of the LDB, so I'm confused.

No, the master user (who has file Create right) starts the

application,
then applies the Netware file attributes Rename Inhibit, Delete
Inhibit,
Shareable to the LDB that Access creates for the backend. When the
master user exits the application, Access doesn't/can't delete the LDB
as it has Delete Inhibit. Effectively, the LDB is always on disk, so
the
ordinary user doesn't need file Create rights.

Not sure what you mean by not deleting the LDB being not a preferred
environment? It works for the applications I support with 100's of
users,
with no more than the usual Access bugs occurrring!

#34

a b <erratticus (AT) gmail (DOT) com> wrote in
news:525eb847-5d0c-425e-adea-d999a942ab52 (AT) l35g2000vbr (DOT) googlegroups.co
m:

Quote:

Not sure what you mean by not deleting the LDB being not a
preferred environment? It works for the applications I support
with 100's of users,
with no more than the usual Access bugs occurrring!

Well, because an LDB file can become corrupted in regular use, it's
good to have it deleted and recreated from scratch. The scenario you
describe is like Access 2 and before, where the LDB file was not
deleted when the last user exited, and Microsoft changed that in Jet
3.x, so that the LDB file is deleted when the last user exits.

All that said, it's not a huge problem, just not the default
operating environment.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

multiple users' simultaneous access to a MS Access database

comp.databases.ms-access comp.databases.ms-access

Re: multiple users' simultaneous access to a MS Access database - 10-07-2010 , 08:17 PM

Re: multiple users' simultaneous access to a MS Access database - 10-08-2010 , 10:36 AM

Re: multiple users' simultaneous access to a MS Access database - 10-11-2010 , 09:20 AM

Re: multiple users' simultaneous access to a MS Access database - 10-11-2010 , 12:43 PM