Remote administer security settings by updating .mdw 2

[votegop]

Anything wrong with remote-administering security settings by distributing updated .mdw's? If my client adds a new employee, I'll need to add their security settings to the .mdw. I don't want this long-distance client to do it themselves (don't want them to belong to ADMINS).

Anyone see a drawback? (BTW - I've searched posts and FAQ)

Jay Evans

 

[tomvdduin]

Michael,

I'm sorry, but what do you mean with the wayward bus? My english isn't that good...

Tom

 

[MichaelRed]

"Wayward bus" is the general notion that accidents and other mis-fortune can and do happen. The specific example is that someone who has important and secret information is run over by a bus which is out of control, The secret and important information is lost forever.

MichaelRed
m.red@att.net

Searching for employment in all the wrong places

 

[tomvdduin]

OK I see... Let me clearify myself: I haven't wrote it right. the inlogname and password of the DB owner are in a sealded enveloppe in the vault. So if something happens to me, someone else can takeover my rights. But I don't want someone else actively can use that account, or have admin rights. However I do want to give someone else the opportunity to add new users...

My question is: What rights do I have to give that particilair person?

greetz

Tom

 

[MichaelRed]

That should be available from the HELP files and your own knowledge of the overall app. I would probably create a small form, write the security access proceudres necessary for the limited activity desired, and make access to the form be limited to a specific Group (or User). Assigning the "alternate" administrator to the group would provide what ever capabilities you include in the code.

MichaelRed
m.red@att.net

Searching for employment in all the wrong places

 

[tomvdduin]

Thanks Michael,

I'm going to work it out... If I have further questions, I'll post them!

For your patience: have a star.

Tom