User Administration

  • Thread starter Thread starter Mike D
  • Start date Start date
M

Mike D

**Some background**

Members of our support group are tasked with
administering somewhere upwards of 400 seperate .mdw
files. When a new user joins the company who needs to be
added to one, many or all of these .mdw's someone has to
manually open each file and add that user. Same thing in
the other direction when someone leaves. Over the past
two years I have developed an Access app that stores the
location of each of the mdw's and can launch a second app
that has functionality for adding & removing users and
changing group memberships and passwords, but this
utility only works on one mdw at a time.

** My Question **

Is there a way to administer user accounts across
multiple mdw files?

Thanks!!!
Mike D
 
You should probably re-think your strategy about multiple MDW files.
That sounds like *way* too many. Are you aware that all users can be
in a single, shared MDW? Are you also aware that a single MDW file can
be used to control the users' permissions in multiple MDB files?
finally, you could probably be assigning permissions to groups, and
make the users members of those groups.

You may find some pertinent information in my security document in the
website in my signature.


**Some background**

Members of our support group are tasked with
administering somewhere upwards of 400 seperate .mdw
files. When a new user joins the company who needs to be
added to one, many or all of these .mdw's someone has to
manually open each file and add that user. Same thing in
the other direction when someone leaves. Over the past
two years I have developed an Access app that stores the
location of each of the mdw's and can launch a second app
that has functionality for adding & removing users and
changing group memberships and passwords, but this
utility only works on one mdw at a time.

** My Question **

Is there a way to administer user accounts across
multiple mdw files?

Thanks!!!
Mike D
Click to expand...


=======================================================
Jack MacDonald
remove UPPERCASE LETTERS from email address
Vancouver, B.C. Canada
Info about MSAccess user-level security
www.geocities.com/jacksonmacd
 
That being the case, you might be able to open another instance of the
DBEngine in a workspace, and connect it to each of the MDW files.
IIRC, the DBEngine object has a SystemDB property that is the MDW.
Once that's open, you could probably manipulate the groups and users
programatically via DAO.

I suggest you explore the DBEngine object and then look on Access Web
for some code for adding/deleting users. There's a link to Access Web
in my signature.

HTH


Jack,

Sadly, we've used this model for about 5 years now.
Thankfully we will be phasing out Access over the next
year and replacing the existing systems with a .NET
solution. For about 3 years now I have been suggesting
the single MDW approach, but I haven't had much luck at
convincing my boss because he can't imagine that he wrote
systems that weren't well planned in the first place and
won't listen to anyone who trys to tell him otherwise.
So I'm trying to find something to ease the suffering of
our support group for the next 13 - 15 months.

Thanks,
Mike D
Click to expand...


=======================================================
Jack MacDonald
remove UPPERCASE LETTERS from email address
Vancouver, B.C. Canada
Info about MSAccess user-level security
www.geocities.com/jacksonmacd
 
Hi Mike,

So far the way I can think out is the same as Jack's, dealing with each mdw
file and add/delete the user account information programmatically.

Please feel free to reply to the threads if you have any questions or if I
misunderstood your concerns.


Sincerely,

Alick Ye, MCSD
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.


--------------------
| Content-Class: urn:content-classes:message
|
| Jack,
|
| Sadly, we've used this model for about 5 years now.
| Thankfully we will be phasing out Access over the next
| year and replacing the existing systems with a .NET
| solution. For about 3 years now I have been suggesting
| the single MDW approach, but I haven't had much luck at
| convincing my boss because he can't imagine that he wrote
| systems that weren't well planned in the first place and
| won't listen to anyone who trys to tell him otherwise.
| So I'm trying to find something to ease the suffering of
| our support group for the next 13 - 15 months.
|
| Thanks,
| Mike D
|
| >-----Original Message-----
| >You should probably re-think your strategy about
| multiple MDW files.
| >That sounds like *way* too many. Are you aware that all
| users can be
| >in a single, shared MDW? Are you also aware that a
| single MDW file can
| >be used to control the users' permissions in multiple
| MDB files?
| >finally, you could probably be assigning permissions to
| groups, and
| >make the users members of those groups.
| >
| >You may find some pertinent information in my security
| document in the
| >website in my signature.
| >
| >
| >On Fri, 12 Sep 2003 13:17:45 -0700, "Mike D"
| <[email protected]>
| >wrote:
| >
| >>**Some background**
| >>
| >>Members of our support group are tasked with
| >>administering somewhere upwards of 400 seperate .mdw
| >>files. When a new user joins the company who needs to
| be
| >>added to one, many or all of these .mdw's someone has
| to
| >>manually open each file and add that user. Same thing
| in
| >>the other direction when someone leaves. Over the past
| >>two years I have developed an Access app that stores
| the
| >>location of each of the mdw's and can launch a second
| app
| >>that has functionality for adding & removing users and
| >>changing group memberships and passwords, but this
| >>utility only works on one mdw at a time.
| >>
| >>** My Question **
| >>
| >>Is there a way to administer user accounts across
| >>multiple mdw files?
| >>
| >>Thanks!!!
| >>Mike D
| >
| >
| >=======================================================
| >Jack MacDonald
| >remove UPPERCASE LETTERS from email
| address
| >Vancouver, B.C. Canada
| >Info about MSAccess user-level security
| >www.geocities.com/jacksonmacd
| >.
| >
|
 
Back
Top