how to get multi user access from single user lice (97)

Topic

New Reply

how to get multi user access from single user license
my I.T. dept told me today that the company only supports single user licenses for access97 & I just developed a database to be shared throughout our regions & found that if one person is in it, nobody else can get in. Basically my front end is an .mde with links to a back end .mdb & it is the back end that is complaining that one person cannot access while another is in it. Any suggestion on how to get out of this dilly of a pickle?

Reply | Quote

Replies

Licences have nothing to do with multi user.
Licences determines the quantities of installations of the program you buy.
Access is always multi user.
Check in Tools | Options, Advanced Tab if the Exclusive option is checked in Default Open Mode. If so check Shared to allow Multi user.

Francois

Reply | Quote

Francois,
I made a new copy of my .mde & verified that the .mde had the settings you specified. I also verified that similar settings were in my backend .mdb my .mde had links to. The error still came up. The ONLY thing I can imagine is that my I.T. did something b/c I sent them a list of user permissions on the .mde & .mdb files. For everyone but myself I told I.T. to set access to the .mde as read only & only I have access to the .mdb, could that mean something?

Reply | Quote

Arage,

I don’t know very much about Networking and Permissions .
Anyway, I don’t think it is a good idee to give read only permissions to your users.
What does Access when it have to write tempory tables or other stuff. I don’t know. Perhaps your IT can tell you more about that.
If you want to secure your mdb’s and mde’s, try with User Security.
It is more flexible and you are the one who grant permissions and not your IT.
A good start to the User Security is :
http://support.microsoft.com/support/acces…tent/secfaq.asp

Francois

Reply | Quote

[indent]

---

For everyone but myself I told I.T. to set access to the .mde as read only

---

[/indent]That’s the reason you’re running into problems. When you open a database on a server (or anywhere else, for that matter), Access opens an LDB file. Every additional user who logs into a database on a server has his lock information added to the existing LDB file. Unless your users have read/write permissions, they can’t write their locks to the LDB file and so they can’t get in.

Reply | Quote

As Charlotte mentioned, you need to give everyone who uses the database full permissions to the network directory containing the backend database. This includes Delete permissions, because the last one out of the database deletes the .ldb file.

Don’t make the .mde read-only. Access writes to that database itself. And the users can’t modify anything anyway, since it is a .mde file.

Reply | Quote

Hi Mark,
Listen to what you

Reply | Quote

I’m sorry, but you misunderstood me. Users must have permissions to the backend as well as the front end. An ldb file is opened on *each* database, frontend, backend, library database, all of them.

Reply | Quote

>>Listen to what you

Reply | Quote

we

Reply | Quote

Arage,

User security will not preventing to delete the file from in Explorer. It is only to grant different level of permissions to each object in the database.
Yes the permissions are transfer from your mdb to your mde file.
For your back-end you’ll have to secure it like your front-end.
For your 2 groups, you’ll have to give appropriate level of permission for each object (Database, tables, queries, form, reports, macros and module) in your databases (front and back-end)
Don’t forget to make backup of your files before beginning with security. The first time you use security, it is very easy to make mistakes (later also ).

Francois

Reply | Quote

tell me this Francois, when I secure my backend, does that mean I

Reply | Quote

Arage,

No, you do not need to create a new workgroup file.
With wrkgadm, join the workgroup you create for your front-end.
Then, start Access and open your back-end with your login (not admin) and run the security wizard.
In the first screen of the security wizard, look at the last two lines which give the username and the workgroup file. If they are OK then proceed with the wizard.

Francois

Reply | Quote

Unfortunately, my security skills aren’t too great. I’d suggest you follow the Compuserve link below to get to the MSDEVAPPS forum, which includes Access (as well as VB, FoxPro, SQL server, etc.). There are 2 files in the forum libraries that will help you:

SECFAQ97.ZIP is a security FAQ, co-authored by Paul Litwin.
SECURE70.EXE is a security whitepaper (also on MS site).

Reply | Quote