Need user logins to work...

[comptechbranden]

I am messing with the user logins and groups. I got it to work on my computer but...It only works on my computer and with every database I open. No other computers get a request for a login and password and the file just opens up.

How can I get a nice login for people at our work?

 

[statsman]

When you install Access on your computer a file called System.mdw is placed on your drive.
It usually resides at
C:\Documents and Settings\Applications Data\Microsoft Office\Office\Access\System.mdw

This file holds all of your settings regarding Access INCLUDING THE SECURITY DETAILS (Users, Passwords etc).

Unless each computer has exactly the same settings in System.mdw, it won't work.
The smart way is to create a new mdw file, give it a different name and link it to all your users.

 

[comptechbranden]

That is a good idea. When you say link it to the users...what do you mean? I need to have it built in the file because I cant have users from other departments being able to open the file on our server and viewing data. Is that possible with what you are talking about?

 

[comptechbranden]

Ok, I am looking at user level and security wizard and I cant change the location of the mdw file. Is there a way to change that to the location of my mdw file on the server?

 

[statsman]

OK
You don't want to move the System.mdw file. There are other people using Access on your network who depend on it. It has their settings too.

You should create a new .mdw file which contains just the settings for your database. Place it on the back end on the server. Then you have to link it to all of the users on the server who are using YOUR database so that these are the settings when they open YOUR database.

 

[comptechbranden]

Ok. So when you say create a new one...How? and when you say link it from the server to the database...How? I feel like im so close to solving this but I am not sure exactly how to do those things...

Thanks.

 

[comptechbranden]

Ok, I give up on this...

My experience is that 97 does not support this feature very well as I have tried everything.

Problem is that it works on my computer the the file will open without asking for user login on any other computer.

I tried all that fancy MDW security file stuff on the server but cant find a way to make every database open with those settings...

 

[gijskerstens]

to force a certain db to use a custom workgroup file, make a shortcut to that file, or to access itself, using the /wrkgrp commandline
for example, you want a db names "2.mdb" located in the root of the D drive to use the workgroup "1" that located in the root of the C:\ drive
the command in the shortcut would then be "d:\2.mdb" /wrkgrp "c:\1.mdw"

 

[Len Boorman]

If you are "messing" with the security wizard, users and permissions the only things you will mess will be, You, Your computer, your database and everybody else in all probability


Access Security will/can do everything you probably want but it is a total minefield for the unwary and the "fiddlers and tweakers"

There are a couple of FAQ documents that go through the security business and explain how to and how not to.

If youi have not read thses you will/are in trouble

If you PM me with an email address I can send them to you as they are too large to post here

Len

PS The most common gross mistake is to play with the system.mdw file.

 

[john471]

Branden,

Len is on the money! Some of the other posts, while well intended, may have mis-represented some facts, or written them in a way that could be mis-interpreted. The posters may not have noticed your footenote that you are using AC97.

Access & Access security can do what you are asking, but it is not the be-all and end-all. If security is "mission critical", Access is not the best place for your data, as there are numerous offerings on the web that can enable the willing to get to your data, assuming their network permissions are such that they have read permission on the file.

That said, here are the steps you need to take.

1) Get the FAQs.
http://support.microsoft.com/default.aspx?scid=/support/access/content/secfaq.asp#_Toc493299666
2) Read the FAQs
3) Re-read the FAQs
4) Follow the step-by-step instructions in the FAQs very carefully and to the letter - do this as a trial run at least once, on a test database.
5) Ensure you take a back up copy of your production database, before you start "messing with" security


No, I am not trying to be cheeky, or imply any level of ability on anyone's part. Access security is difficult to get right, and it is very easy to mis-understand and "implement" incorrectly. Conversely, it takes a some understanding, learning, and experience to implement correctly.

Your statements, above, are indicative of an incorrect implementation of Access security.
Point #32 in the linked FAQ above, deals with one of your questions.
32. I thought I helped protect the security of my database, but someone opened it with his or her own workgroup file. Is Microsoft Access security broken?

When implemented correctly, it is very good for keeping out all but those with serious intent, and keeping sets of users (groups) on the straight and narrow.

HTH

Regards

John