[AccessD] Basic Question (Probably) that I just don't know

[Jim Dettman]

 On the FE it doesn't matter, unless it is shared as you said, which some
do.

Jim. 

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Bill Benson
Sent: Friday, September 23, 2016 02:55 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Basic Question (Probably) that I just don't know

Why would it matter that the front end is opened exclusively? It's the
backend that matters, right? Don't you give all users their own front end?
(I do). I don't have a front end sitting in a shared folder that everyone
accesses (no pun intended, but I like it).
On Sep 22, 2016 3:04 PM, "Jim Dettman" <jimdettman at verizon.net> wrote:

>  <<If I understand correctly, you are saying that there are settings with
> the DB for this? I wouldn't think she'd have done anything differently,
but
> this would make sense.>>
>
>   Access settings (with a DB open, it's under File, Options, Client
> Settings, Default Open Mode).   If one user has their settings defaulted
to
> "exclusive", then even if the privs are right, only that person will have
> access to the DB if their the first in, and if not the first in, they
won't
> be able to open it.
>
>   Like wise if they have a shortcut with the /excl switch (rare - but I've
> seen setups for admins where they have a shortcut on the desktop with
this,
> and then use it out of habit).
>
>  Everyone should have this setting as "Shared", and have full privs for
the
> FE/BE directories and then you shouldn't have any problems.
>
> Jim.
>
>
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> John Clark
> Sent: Thursday, September 22, 2016 01:59 PM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Basic Question (Probably) that I just don't know
>
>
> "If more than one can't open it, then that's Access settings (Shared or
> exclusive) or privs on the directory."
> Bingo...this is the issue. And I never really saw it as an "issue"
> really...just the way it is. If we needed multiple users I suggested
> splitting the DB, and if a user was a single access user it didn't matter.
>
> This is an amateur user and she just wanted to know why one single DB did
> this for her. And I was really unable to give her a concrete answer, so
I'm
> looking to fill that gap in my knowledge.
>
> If I understand correctly, you are saying that there are settings with the
> DB for this? I wouldn't think she'd have done anything differently, but
> this
> would make sense.
>
>
>
>
> Notice: This electronic transmission is intended for the sole use of the
> individual or entity to which it is addressed and may contain
confidential,
> privileged or otherwise legally protected information. If you are not the
> intended recipient, or if you believe you are not the intended recipient,
> you are hereby notified that any use, disclosure, copying, distribution,
or
> the taking of any action in reliance on the contents of this information,
> is
> strictly prohibited. Niagara County is not responsible for the content of
> any external hyperlink referenced in this email or any email.
> IF YOU HAVE RECEIVED THIS TRANSMISSION IN ERROR, PLEASE NOTIFY THE SENDER
> IMMEDIATELY BY EMAIL AND DELETE THE ORIGINAL MESSAGE ALONG WITH ANY PAPER
> OR
> ELECTRONIC COPIES.
> Thank you for your cooperation.
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com