How to Distribute New Objects to Site wtih Remote MDW?

[kiln]

I have a fully secured Access 2000 app that will be distributed to
remote sites; sites I'll never have access to, physically or over the
wire. The app is secured per the sec faq using the dev mdw and user mdw,
so that the site admin can add users and assign limited perms. I'm not
sure of the easiest route to take when it comes to deploying revisions
to the front end file (the mde with forms queries etc). Perms for any
new objects will not be covered by the remote mdw files. I won't be able
to "remake" the mdw files, I need to somehow adapt them to deal with the
new objects. Do I have to build an inventory module, and assign perms
via code? I've never done that; sounds like a lot of work??? Anyone been
through that? Have an alternate approach?

This is really the first time I've thought this through and it just
occurred to me...I can't see how this could be done without distributing
the dev mdw file. Which of course I don't want to do. gaahhh.

Thanks

 

[TC]

I have a fully secured Access 2000 app that will be distributed to
remote sites; sites I'll never have access to, physically or over the

wire. The app is secured per the sec faq using the dev mdw and user mdw,
so that the site admin can add users and assign limited perms. I'm not
sure of the easiest route to take when it comes to deploying revisions
to the front end file (the mde with forms queries etc). Perms for any

new objects will not be covered by the remote mdw files. I won't be able
to "remake" the mdw files, I need to somehow adapt them to deal with the
new objects.

(snip)

That is the argument for assigning permissions only to groups, not to
users.

Say you have a group 'X' in both mdw's (dev & prod). Say all object
perms are applied to that group, not to any users within it.

Say you add a new object 'Y' to the FE. Using your *dev* mdw, you
assign perm 'Z' on that object, to group 'X'. If group 'X' has
precisely the same name *and PID* in the *prod* mdw, the members of
that group (in the *prod* mdw) will automatically receive the new perm
('Z') to the new object ('Y') in the new FE.

The issue of group vs. user perms has been comprehensively aired
before. Some people say you should *never* assign permissions directly
to users. I do not agree with that, but YMMV. Do some googling & you'll
find lots more comment about this issue.

HTH,
TC

 

[kiln]

Right I forgot the basics...I believe you're right, and that I was
worried without cause. I am using groups not users as the basis for
perms. I was prompted to my conclusion by a quick test, using a newly
created object and one of the site logins, and perms were denied. But I
realize now that I didn't set the perms for the user oriented groups, so
of course perms were denied.

Thanks for helping me come to my senses!

 

[TC]

No probs, good luck!

TC