> Is it possible to password protect a specific table or query in an Access
> database?

Yes. Place that specific table or query in an Access database that has
either user-level or shared-level security applied. The user must use a
password to open that database.

This probably isn't the answer you were hoping for, but if the user can
access the database window in the current database, then the table or query
will immediately open without any interference on the developer's part, as
long as the user has appropriate security permissions assigned, even if the
table is linked to a password-protected database. If the user doesn't have
appropriate security permissions for the object, then the user will receive
an error message stating this. There's no way for the developer to
interject a password to hinder the user.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)


"SusieC" <(E-Mail Removed)> wrote in message
news:770AD1DB-A2C2-4FB4-B08A-(E-Mail Removed)...
> Is it possible to password protect a specific table or query in an Access
> database?

Hi, Susie.

You're welcome!

> this sentence intrigued me: If the user doesn't have
> appropriate security permissions for the object...

You've got the idea. If user-level security is applied to an object, then
users who don't have permissions will be unable to open that object, even if
they can see the object's name in the database window and double-click on
it, so there's no need for a separate password.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)


"Susie C" <Susie (E-Mail Removed)> wrote in message
news88CDFD1-4284-43A6-A748-(E-Mail Removed)...
> Thank you.....this sentence intrigued me: If the user doesn't have
> > appropriate security permissions for the object...
> I will see about this solution.
> Thank you!
> "'69 Camaro" wrote:
>
> > > Is it possible to password protect a specific table or query in an
Access
> > > database?
> >
> > Yes. Place that specific table or query in an Access database that has
> > either user-level or shared-level security applied. The user must use a
> > password to open that database.
> >
> > This probably isn't the answer you were hoping for, but if the user can
> > access the database window in the current database, then the table or
query
> > will immediately open without any interference on the developer's part,
as
> > long as the user has appropriate security permissions assigned, even if
the
> > table is linked to a password-protected database. If the user doesn't
have
> > appropriate security permissions for the object, then the user will
receive
> > an error message stating this. There's no way for the developer to
> > interject a password to hinder the user.
> >
> > HTH.
> >
> > Gunny
> >
> > See http://www.QBuilt.com for all your database needs.
> > See http://www.Access.QBuilt.com for Microsoft Access tips.
> >
> > (Please remove ZERO_SPAM from my reply E-mail address, so that a message
> > will be forwarded to me.)
> >
> >
> > "SusieC" <(E-Mail Removed)> wrote in message
> > news:770AD1DB-A2C2-4FB4-B08A-(E-Mail Removed)...
> > > Is it possible to password protect a specific table or query in an
Access
> > > database?
> >
> >
> >

Thanks for asking that question Susie C!

Hi "69 Camaro".
This question pertains to the same problem that I'm having, but I have one
more question for you. The table that we are using to update information will
be on a shared drive; we have the user files setup and the password. The
problem is, when I am updating information in the table and then one of my
co-workers come onto the same database and goes into the same tables that I’m
in to update it…it doesn’t tell them that I’m in the file already…it just
lets them come right in table and start typing away. We switched from Excel
to Access to prevent duplicates like this...do you have any suggestions for
me?

T. Anderson

"'69 Camaro" wrote:

> Hi, Susie.
>
> You're welcome!
>
> > this sentence intrigued me: If the user doesn't have
> > appropriate security permissions for the object...
>
> You've got the idea. If user-level security is applied to an object, then
> users who don't have permissions will be unable to open that object, even if
> they can see the object's name in the database window and double-click on
> it, so there's no need for a separate password.
>
> Gunny
>
> See http://www.QBuilt.com for all your database needs.
> See http://www.Access.QBuilt.com for Microsoft Access tips.
>
> (Please remove ZERO_SPAM from my reply E-mail address, so that a message
> will be forwarded to me.)
>
>
> "Susie C" <Susie (E-Mail Removed)> wrote in message
> news88CDFD1-4284-43A6-A748-(E-Mail Removed)...
> > Thank you.....this sentence intrigued me: If the user doesn't have
> > > appropriate security permissions for the object...
> > I will see about this solution.
> > Thank you!
> > "'69 Camaro" wrote:
> >
> > > > Is it possible to password protect a specific table or query in an
> Access
> > > > database?
> > >
> > > Yes. Place that specific table or query in an Access database that has
> > > either user-level or shared-level security applied. The user must use a
> > > password to open that database.
> > >
> > > This probably isn't the answer you were hoping for, but if the user can
> > > access the database window in the current database, then the table or
> query
> > > will immediately open without any interference on the developer's part,
> as
> > > long as the user has appropriate security permissions assigned, even if
> the
> > > table is linked to a password-protected database. If the user doesn't
> have
> > > appropriate security permissions for the object, then the user will
> receive
> > > an error message stating this. There's no way for the developer to
> > > interject a password to hinder the user.
> > >
> > > HTH.
> > >
> > > Gunny
> > >
> > > See http://www.QBuilt.com for all your database needs.
> > > See http://www.Access.QBuilt.com for Microsoft Access tips.
> > >
> > > (Please remove ZERO_SPAM from my reply E-mail address, so that a message
> > > will be forwarded to me.)
> > >
> > >
> > > "SusieC" <(E-Mail Removed)> wrote in message
> > > news:770AD1DB-A2C2-4FB4-B08A-(E-Mail Removed)...
> > > > Is it possible to password protect a specific table or query in an
> Access
> > > > database?
> > >
> > >
> > >
>
>
>

P.S.
I bumped into an option that is called "Default Record Locking" under the
options tab. Will this be helpful to me? To lock the query and have people
update the query instead of the table? Do you happen to know the Pros and
Cons of using this option?

Thanks again!
T.

"Anderson" wrote:

> Thanks for asking that question Susie C!
>
> Hi "69 Camaro".
> This question pertains to the same problem that I'm having, but I have one
> more question for you. The table that we are using to update information will
> be on a shared drive; we have the user files setup and the password. The
> problem is, when I am updating information in the table and then one of my
> co-workers come onto the same database and goes into the same tables that I’m
> in to update it…it doesn’t tell them that I’m in the file already…it just
> lets them come right in table and start typing away. We switched from Excel
> to Access to prevent duplicates like this...do you have any suggestions for
> me?
>
> T. Anderson
>
> "'69 Camaro" wrote:
>
> > Hi, Susie.
> >
> > You're welcome!
> >
> > > this sentence intrigued me: If the user doesn't have
> > > appropriate security permissions for the object...
> >
> > You've got the idea. If user-level security is applied to an object, then
> > users who don't have permissions will be unable to open that object, even if
> > they can see the object's name in the database window and double-click on
> > it, so there's no need for a separate password.
> >
> > Gunny
> >
> > See http://www.QBuilt.com for all your database needs.
> > See http://www.Access.QBuilt.com for Microsoft Access tips.
> >
> > (Please remove ZERO_SPAM from my reply E-mail address, so that a message
> > will be forwarded to me.)
> >
> >
> > "Susie C" <Susie (E-Mail Removed)> wrote in message
> > news88CDFD1-4284-43A6-A748-(E-Mail Removed)...
> > > Thank you.....this sentence intrigued me: If the user doesn't have
> > > > appropriate security permissions for the object...
> > > I will see about this solution.
> > > Thank you!
> > > "'69 Camaro" wrote:
> > >
> > > > > Is it possible to password protect a specific table or query in an
> > Access
> > > > > database?
> > > >
> > > > Yes. Place that specific table or query in an Access database that has
> > > > either user-level or shared-level security applied. The user must use a
> > > > password to open that database.
> > > >
> > > > This probably isn't the answer you were hoping for, but if the user can
> > > > access the database window in the current database, then the table or
> > query
> > > > will immediately open without any interference on the developer's part,
> > as
> > > > long as the user has appropriate security permissions assigned, even if
> > the
> > > > table is linked to a password-protected database. If the user doesn't
> > have
> > > > appropriate security permissions for the object, then the user will
> > receive
> > > > an error message stating this. There's no way for the developer to
> > > > interject a password to hinder the user.
> > > >
> > > > HTH.
> > > >
> > > > Gunny
> > > >
> > > > See http://www.QBuilt.com for all your database needs.
> > > > See http://www.Access.QBuilt.com for Microsoft Access tips.
> > > >
> > > > (Please remove ZERO_SPAM from my reply E-mail address, so that a message
> > > > will be forwarded to me.)
> > > >
> > > >
> > > > "SusieC" <(E-Mail Removed)> wrote in message
> > > > news:770AD1DB-A2C2-4FB4-B08A-(E-Mail Removed)...
> > > > > Is it possible to password protect a specific table or query in an
> > Access
> > > > > database?
> > > >
> > > >
> > > >
> >
> >
> >

Hi.

> > The
> > problem is, when I am updating information in the table and then one of
my
> > co-workers come onto the same database and goes into the same tables
that I'm
> > in to update it.it doesn't tell them that I'm in the file already.it
just
> > lets them come right in table and start typing away.

Access is designed to be used in a multiuser environment. Jet won't let
more than one user edit the same record at the same time, so you don't need
to worry about loss of data integrity. The other user may edit other
records while you edit your own record in the same table.

> > do you have any suggestions for
> > me?

If you want all other users to stay out of the database while you are using
it, then open it in exclusive mode. Other users will be warned that the
database is locked by 'UserName' on 'ComputerName' and won't be able to open
the database again until you close it. If you want to just keep the other
users out of any table while you edit it, then allow everyone to open the
database in shared mode, but set the default record locking option to "All
records." This will be rather constricting, though, because this applies to
all tables in the database, not just one. All other users will be locked
out of any table while one person edits it.

> I bumped into an option that is called "Default Record Locking" under the
> options tab. Will this be helpful to me?

Perhaps. The default record locking option will allow you to set the record
locking scheme to optimistic locking (No locks), pessimistic locking (Edited
record), and table-level locking (All records). As mentioned above, the
table-level locking will lock other users out of the entire table while you
edit it. The optimistic locking is the least restrictive and doesn't lock
the record until the record is actually saved. Pessimistic locking locks
the record immediately when a user starts to edit the record and doesn't
release the lock until the record is saved. The more users using the table,
the more often records are locked, which seriously limits the database
performance and aggravates users.

"Open database using record-level locking" option is available in Access 2K
and newer versions. It can be set to record-level locking instead of
page-level locking, as long as DAO is not being used and the first computer
that connects to the database has this option set on record-level. All
others that connect to the database afterwards will use the same setting
while the database is open, regardless of what their own settings are.

> To lock the query and have people
> update the query instead of the table?

One cannot lock a query. The query is based upon the records in the table
or tables. When the SELECT query is updated, the records in the tables are
updated.

> Do you happen to know the Pros and
> Cons of using this option?

Pros and cons are listed above, but they apply to the tables where the
records are stored, not queries, because queries don't store records.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)


"Anderson" <(E-Mail Removed)> wrote in message
news:E54FA5E7-91EA-4833-BB53-(E-Mail Removed)...
> P.S.
> I bumped into an option that is called "Default Record Locking" under the
> options tab. Will this be helpful to me? To lock the query and have people
> update the query instead of the table? Do you happen to know the Pros and
> Cons of using this option?
>
> Thanks again!
> T.
>
> "Anderson" wrote:
>
> > Thanks for asking that question Susie C!
> >
> > Hi "69 Camaro".
> > This question pertains to the same problem that I'm having, but I have
one
> > more question for you. The table that we are using to update information
will
> > be on a shared drive; we have the user files setup and the password. The
> > problem is, when I am updating information in the table and then one of
my
> > co-workers come onto the same database and goes into the same tables
that I'm
> > in to update it.it doesn't tell them that I'm in the file already.it
just
> > lets them come right in table and start typing away. We switched from
Excel
> > to Access to prevent duplicates like this...do you have any suggestions
for
> > me?
> >
> > T. Anderson
> >
> > "'69 Camaro" wrote:
> >
> > > Hi, Susie.
> > >
> > > You're welcome!
> > >
> > > > this sentence intrigued me: If the user doesn't have
> > > > appropriate security permissions for the object...
> > >
> > > You've got the idea. If user-level security is applied to an object,
then
> > > users who don't have permissions will be unable to open that object,
even if
> > > they can see the object's name in the database window and double-click
on
> > > it, so there's no need for a separate password.
> > >
> > > Gunny
> > >
> > > See http://www.QBuilt.com for all your database needs.
> > > See http://www.Access.QBuilt.com for Microsoft Access tips.
> > >
> > > (Please remove ZERO_SPAM from my reply E-mail address, so that a
message
> > > will be forwarded to me.)
> > >
> > >
> > > "Susie C" <Susie (E-Mail Removed)> wrote in message
> > > news88CDFD1-4284-43A6-A748-(E-Mail Removed)...
> > > > Thank you.....this sentence intrigued me: If the user doesn't have
> > > > > appropriate security permissions for the object...
> > > > I will see about this solution.
> > > > Thank you!
> > > > "'69 Camaro" wrote:
> > > >
> > > > > > Is it possible to password protect a specific table or query in
an
> > > Access
> > > > > > database?
> > > > >
> > > > > Yes. Place that specific table or query in an Access database
that has
> > > > > either user-level or shared-level security applied. The user must
use a
> > > > > password to open that database.
> > > > >
> > > > > This probably isn't the answer you were hoping for, but if the
user can
> > > > > access the database window in the current database, then the table
or
> > > query
> > > > > will immediately open without any interference on the developer's
part,
> > > as
> > > > > long as the user has appropriate security permissions assigned,
even if
> > > the
> > > > > table is linked to a password-protected database. If the user
doesn't
> > > have
> > > > > appropriate security permissions for the object, then the user
will
> > > receive
> > > > > an error message stating this. There's no way for the developer
to
> > > > > interject a password to hinder the user.
> > > > >
> > > > > HTH.
> > > > >
> > > > > Gunny
> > > > >
> > > > > See http://www.QBuilt.com for all your database needs.
> > > > > See http://www.Access.QBuilt.com for Microsoft Access tips.
> > > > >
> > > > > (Please remove ZERO_SPAM from my reply E-mail address, so that a
message
> > > > > will be forwarded to me.)
> > > > >
> > > > >
> > > > > "SusieC" <(E-Mail Removed)> wrote in message
> > > > > news:770AD1DB-A2C2-4FB4-B08A-(E-Mail Removed)...
> > > > > > Is it possible to password protect a specific table or query in
an
> > > Access
> > > > > > database?
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >