Workgroups & Distribution of my Application

[Guest]

Hi,

I created an application to manage information requests to our department
and I have to created three groups -

Admins - ME (and whomever else my boss wants in there).

Our team - with rights to add and modify records but not able to delete
from the table or alter the design of the objects.

Admin-Users - with rights to insert and view records. However I don't want
them to have to sign in.

I have envoked the security wizard and I'm having a few difficulties.

I have the white paper regarding security (page 12) and tried to use the
/user name /password in the microsoft program manager to allow me to enter
into the db as ADMIN (without a password) but when I use the shortcut it's
logging me on as myself.

I understand that by using the shortcut on my desktop it is using my profile
from the .mdw associated with the db. What I don't understand is how do I
deploy this on the network so that my coworkers that are in the Our Team
group will be prompted to sign in. Do I have to have them join the workgroup
at their workstation? Do they have to use my shortcut? If so is it ok to send
the shortcut via email?

Also, how do I make sure that the Admin group gets the rights I gave them?
Is this also a shortcut issue? If the shortcut is placed out on our intranet
will that do the trick? I don't want to have to add people to the Admin-Users
group because there is a possibility of >600 employees that might need to
access this db to submit a request to our department at any given time.

Sorry for all the questions. I've been banging away at this problem for
about 3 months and have read almost every post I can find about security. I
can get it to work properly on my desktop but when I test for other users at
other workstations usually they have full rights to the DB which means their
not accessing the correct .mdw. How can this be accomplished?

Help!
Thanks!
A

 

[Joan Wild]

I created an application to manage information requests to our department
and I have to created three groups -

Admins - ME (and whomever else my boss wants in there).

Our team - with rights to add and modify records but not able to delete
from the table or alter the design of the objects.

Admin-Users - with rights to insert and view records. However I don't want
them to have to sign in.

Since you have assigned permissions to the Users Group, they can just use
their standard system.mdw that ships with Access. They'll get no login, but
be restricted by the permissions for the Users Group.

I have envoked the security wizard and I'm having a few difficulties.

I have the white paper regarding security (page 12) and tried to use the
/user name /password in the microsoft program manager to allow me to enter
into the db as ADMIN (without a password) but when I use the shortcut it's
logging me on as myself.

It just defaults to your username. You can edit that to your liking.

I understand that by using the shortcut on my desktop it is using my
profile
from the .mdw associated with the db. What I don't understand is how do I
deploy this on the network so that my coworkers that are in the Our Team
group will be prompted to sign in. Do I have to have them join the
workgroup
at their workstation? Do they have to use my shortcut? If so is it ok to
send
the shortcut via email?

Put the mdw file on the network, and give them a shortcut. Providing they
have Access installed in the same folder as you, then yes you can send the
shortcut.

With multiple users, you should split the database and put the backend on
the server with the mdw file. Give each user a copy of the frontend on
their computer, linked to the tables in the backend.

Also, how do I make sure that the Admin group gets the rights I gave them?
Is this also a shortcut issue? If the shortcut is placed out on our
intranet
will that do the trick? I don't want to have to add people to the
Admin-Users
group because there is a possibility of >600 employees that might need to
access this db to submit a request to our department at any given time.

No need for them to even use your mdw; have them just use Access, and it
will use the standard system.mdw workgroup.