Re: Different MDW files
- From: Don Barton <DonaldB627@xxxxxxxxx>
- Date: Fri, 22 Jun 2007 13:57:01 -0000
Albert,
Thanks for your clear and detailed answer to my questions. My
response is below.
On Jun 21, 7:43 pm, "Albert D. Kallal" <PleaseNOOOsPAMmkal...@xxxxxxx>
wrote:
If you need to get/see the current workgroup file, then hit ctrl-g, and in
the debug window type:
? SysCmd(acSysCmdGetWorkgroupFile)
This is good to know. Thanks for the tip!
If you override, then what sense
does it make to use that menu option to join a workgroup? I do think this is
a *sort of* a bug (but it simply shows the DEFAULT workgroup file you *will*
be attached to, not the current one. So, it never did show the current
workgroup...it just shows the default one you will be attached to.
The fact that MS lists the default workgroup file in the Workgroup
Admistrators, regardless if it is not the one being used, is in my
opinion, misleading and confusing. You don't know how many times I
went back and changed the thing, only to have it change back to the
default (note: it was a "new" default each time; system1.mdw,
system2.mdw, etc.. even more confusing) I finally settled on using
ONLY the wizard, and now security works as I expected it to.
You should NEVER NEVER set security for a form, report, query etc to a
actual INDIVIDUAL!!! The INSTANT you do this, you have now in fact put
security for users in the mdb file. That means if you send an update
to your client, then you loose current settings.
So, you have 100% complete freedom to
email, or simply update your users front end.
This is what I wanted to hear. I do expect to be able to update FE
via email. But how to keep the mdw sync'd was something I hadn't
figured out. This is a huge fact and answers my concerns. The golden
rule is then: New Access objects are assigned to security groups -
never to individuals!!
http://www.members.shaw.ca/AlbertKallal/Articles/UseAbility/UserFriendly.htm
Like I did, you might want to spend part of a afternoon, and make a fewI would very much like to see a copy of your security manager.
nice security manager screens that makes this stuff VERY easy for your
clients.
I have not posted my "security" manager, but I can email you a copy if you
wish...
Assigning security should not be the job of the developer, but the
client. I had thought of writing my own routines, but it sounds like
you've done something very similar already.
Thanks again,
You've been very helpful,
Don
.
- References:
- Different MDW files
- From: Don Barton
- Re: Different MDW files
- From: Albert D. Kallal
- Different MDW files
- Prev by Date: Disable Security - help!
- Next by Date: Re: Prevent Importing / Linkage via Security
- Previous by thread: Re: Different MDW files
- Next by thread: Re: Problems creating MDE file
- Index(es):
Relevant Pages
|