By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,696 Members | 2,213 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,696 IT Pros & Developers. It's quick & easy.

Access Security Questions

P: n/a
I'm working on a database for a local business that requires
different security for different individuals. There is one PC at the
front desk and several individuals will be working with the database
throughout the day. I haven't worked with the Access Security
wizard but have this question - will different individuals be able to
sign on and off of the database on this PC without logging on to the PC
itself? That is to say, will the security ask for a user name when
the database is opened, or does it do something with who is signed on
to the PC when the database is opened?

Thanks for the assistance

Nov 13 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
"mar10" <ma****@yahoo.com> wrote in message
news:11**********************@g44g2000cwa.googlegr oups.com...
I'm working on a database for a local business that requires
different security for different individuals. There is one PC at the
front desk and several individuals will be working with the database
throughout the day. I haven't worked with the Access Security
wizard but have this question - will different individuals be able to
sign on and off of the database on this PC without logging on to the PC
itself? That is to say, will the security ask for a user name when
the database is opened, or does it do something with who is signed on
to the PC when the database is opened?


Access user level security prompts for login when you open the file.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 13 '05 #2

P: n/a
Br
Rick Brandt <ri*********@hotmail.com> wrote:
"mar10" <ma****@yahoo.com> wrote in message
news:11**********************@g44g2000cwa.googlegr oups.com...
I'm working on a database for a local business that requires
different security for different individuals. There is one PC at the
front desk and several individuals will be working with the database
throughout the day. I haven't worked with the Access Security
wizard but have this question - will different individuals be able to
sign on and off of the database on this PC without logging on to the
PC itself? That is to say, will the security ask for a user name
when the database is opened, or does it do something with who is
signed on to the PC when the database is opened?


Access user level security prompts for login when you open the file.


If you're using Access97 or previous Access will prompt you when Access
is opened.
If you're using Access2000 or later Access will prompt you when you open
a database.
....when attached to a non default workgroup file.

Access JET security can't use WindowsNT security. If you use MSSQL or
similar as the backend then you can take advantage of it.
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response
Nov 13 '05 #3

P: n/a
If you're using Access97 or previous Access will prompt you when Access
is opened.
If you're using Access2000 or later Access will prompt you when you open
a database.
...when attached to a non default workgroup file.

Never seen any difference in this respect between A97 and A2k.
If I open A2k with the default workgroup and try to open a secured mdb (using a different workgroup) Access tells me that I don't have the necessary permissions .....
Same with A97 here ...
Same with Access 2.0

If I am 'attached to' or 'using' a different mdw (or mda in previous versions) Access *always* prompts me.
This is just the way the security 'works'.
IME you can even open all your secured mdb's with the same login using different mdw-files for the mdb's.
This, of course, implies that you have created the *same* user with the *same* pid in the different mdw-files ...

Arno R
Nov 13 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.