log in problems

[Sal]

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.

 

[Joan Wild]

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.

Then you missed a step in securing it. Download and study the Security FAQ
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:
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?

This may be a windows permission problem. Do all users have
read,write,create,delete permissions on the folder? Do they all have K:
mapped to the same location?

 

[EarlM]

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]

Anything you recommend to read to start with?

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

 

[EarlM]

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