|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
log in problemsWhen I first created the access db I created it on a local drive. There I
created the log ins and security permissions. Everything was working fine. I recently moved it to a network drive only to discover the users I had set up would bypass the login screen. I then moved my security files from my C: drive to the network K: drive. Now I'm getting an error message that my users do not have permission to access the database, before they even receive a log in prompt. What have I done wrong? Help! Thanks. Sal wrote:
> When I first created the access db I created it on a local drive. Then you missed a step in securing it. Download and study the Security FAQ> There I created the log ins and security permissions. Everything > was working fine. I recently moved it to a network drive only to > discover the users I had set up would bypass the login screen. http://support.microsoft.com/?id=207793 Security Whitepaper http://support.microsoft.com/?id=148555 Although the whitepaper is old, it contains information to help you understand security. I've also outlined the detailed steps at www.jmwild.com/AccessSecurity.htm I > then moved my security files from my C: drive to the network K: This may be a windows permission problem. Do all users have > drive. Now I'm getting an error message that my users do not have > permission to access the database, before they even receive a log in > prompt. What have I done wrong? read,write,create,delete permissions on the folder? Do they all have K: mapped to the same location? -- Joan Wild Microsoft Access MVP How are they opening the database? If they are double clicking on the file,
they are perhaps getting the correct result. Place a short cut on their desktop that is something like the following: "C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "E:\FolderName\DBName.MDB" /excl /wrkgrp "E:\FolderName\SYSTEM.MDW /Runtime" You may want to remove the /Runtime for your PC. If this is an application with forms & reports, not just a shared file where users make changes directly to the tables (bad choice), you should split the database. Place the front end on each workstation and the backend on the server. There's tons of literature on how to accomplish this. EarlM Show quoteHide quote "Sal" wrote: > When I first created the access db I created it on a local drive. There I > created the log ins and security permissions. Everything was working fine. > I recently moved it to a network drive only to discover the users I had set > up would bypass the login screen. I then moved my security files from my C: > drive to the network K: drive. Now I'm getting an error message that my > users do not have permission to access the database, before they even receive > a log in prompt. What have I done wrong? Help! Thanks. Anything you recommend to read to start with?
Show quoteHide quote "EarlM" wrote: > How are they opening the database? If they are double clicking on the file, > they are perhaps getting the correct result. Place a short cut on their > desktop that is something like the following: > > "C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" > "E:\FolderName\DBName.MDB" /excl /wrkgrp "E:\FolderName\SYSTEM.MDW /Runtime" > > You may want to remove the /Runtime for your PC. If this is an application > with forms & reports, not just a shared file where users make changes > directly to the tables (bad choice), you should split the database. Place > the front end on each workstation and the backend on the server. There's > tons of literature on how to accomplish this. > > EarlM > > > > "Sal" wrote: > > > When I first created the access db I created it on a local drive. There I > > created the log ins and security permissions. Everything was working fine. > > I recently moved it to a network drive only to discover the users I had set > > up would bypass the login screen. I then moved my security files from my C: > > drive to the network K: drive. Now I'm getting an error message that my > > users do not have permission to access the database, before they even receive > > a log in prompt. What have I done wrong? Help! Thanks. Sal, I like "Access 2002 Desktop Developer's Handbook" by Litwin, Getz, and
Gunderluy (Sybex). Volume 2, the "Enterprise Developer's Handbook" is a bit more advanced, so start with Volume 1. Their Access 2000 version is almost as good, but get the 2002 one if you can. EarlM Show quoteHide quote "Sal" wrote: > Anything you recommend to read to start with? > > "EarlM" wrote: > > > How are they opening the database? If they are double clicking on the file, > > they are perhaps getting the correct result. Place a short cut on their > > desktop that is something like the following: > > > > "C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" > > "E:\FolderName\DBName.MDB" /excl /wrkgrp "E:\FolderName\SYSTEM.MDW /Runtime" > > > > You may want to remove the /Runtime for your PC. If this is an application > > with forms & reports, not just a shared file where users make changes > > directly to the tables (bad choice), you should split the database. Place > > the front end on each workstation and the backend on the server. There's > > tons of literature on how to accomplish this. > > > > EarlM > > > > > > > > "Sal" wrote: > > > > > When I first created the access db I created it on a local drive. There I > > > created the log ins and security permissions. Everything was working fine. > > > I recently moved it to a network drive only to discover the users I had set > > > up would bypass the login screen. I then moved my security files from my C: > > > drive to the network K: drive. Now I'm getting an error message that my > > > users do not have permission to access the database, before they even receive > > > a log in prompt. What have I done wrong? Help! Thanks.
How Do I Prevent Access 2003 Crash when using Digital ID & Library
Installed updates, now macros don't work! User level security 2002 / 2003 Design Master security workgroup information file (WIF) problem security applied to all my DBs digital signature trouble Missing User data on some macros stops conversion of Access97 to Access2003 logon Testing Database Security |
|||||||||||||||||||||||