[Lotek]

I'm Making a Database that can be "viewed" by many people at the same time but changed by only a few. problem is when I put it into a folder and make the folder read only, we can't change or update the database while some one is viewing it. If I don't put it into a Read only file it will work, but then when one of the other workers who can change the info does, that changes the Security on that file so that everyone has full change rights to it. any Ideas would be helpful.

[Anne Troy]

Look into making an mde file.

[downwitchyobadself]

You need Access security. Add users and groups, and set their permissions accordingly. Searching Access help for security should do the trick.

I can't tell from your post if you mean that you need to make your data read-only, or your objects, i.e. forms, reports, code, etc. If it's the objects, and mde file is the way to go, as Dreamboat suggests. But mdes cannot be updated. I suspect you only want the data read-only for some users, write for others.

Let us know.

[Denise Shaw]

I'm so glad you asked that Lotek. I need to know that info too. I tried setting permissions and it messed up my whole database. I was confused about the Admin rights and Owner rights. Who is the owner? And if you are the owner, what does that do the User's. Fortunately, I backed up my database and was able to restore it. Let us know how you make out.

[Anne Troy]

Might want to check here.

ALWAYS, ALWAYS, before doing security, put a copy of your database somewhere else!

By default, everyone is Admin. The most common problem (if I recall) is that you go in as an Admin, make yourself the owner, and then close and try to get back in as an Admin when the only person who has rights is owner at that point. Something like that. Anyway, where I work, we don't even offer much help with security (at least from the outset), we just send them this:

http://support.microsoft.com/default...;en-us;Q165009

[downwitchyobadself]

Dreamboat's right on. Except that I believe that the person who implements the security first time around normally becomes owner.

Whatever. I myself don't use it (I don't trust anyone locking down my stuff for me), but the link is a good explanation, and unless you're very comfy with VBA and can manipulate who can do what through another setup (which is what I do, tedium tedium), security's still your best bet.

[Denise Shaw]

As usual Dreamboat, you were a big help. I'll check that sight. This subject has been a thorn in my side for quite some time. Unfortunately, I think it's the way we log in. We log into the network which gives us access to the drive that the database is on. Do we need to set a log into the database?

[Lotek]

Again You guys drug me out of the fire it worked Great. Setup up my users and it worked great now we can edit and read all at the same time.