Re: Should we Convert to Access 2007?

Thanks Larry,

The reason I copied it was because the secure.mdw file does not get
installed with Access 2007. I copied it over from one pc that had
Access 2003 to the one that had Access 2007. It was the only way I
could think of to get those new databases to open without prompting
for a login name and password. Is there another way to disable a
joined workgroup in Access 2007?




On Feb 28, 7:51 pm, "Larry Linson" <boun...@xxxxxxxxxxxxx> wrote:
"WPW07" <wwisnie...@xxxxxxxxx> wrote

I came up with an interesting solution. I was able to copy the
default system.mdw file from Access 2003 over to Access 2007. Then
using the RunCommand acCmdWorkgroupAdministrator Module I created I
could join the default system.mdw i just copied over. No more
prompting for the name and password!

Many of us find it more useful and convenient to use a shortcut specifying
the .MDW to be used with a particular application than to "join" an .MDW.

If you download and read the Security FAQ, and search the archives of this
newsgroup, you may find that copying a default .MDW may not be as secure as
you'd like.

Larry Linson
Microsoft Office Access MVP

.

Relevant Pages

  • Re: New to security have questions before plunging
    ... Joan Wild wrote: ... There is no reason to create a new MDW for each revision; infact it's undesireable (when to deploy it, you'll wipe out the users' passwords.) ... Remember that the permissions are stored in the mdb not the mdw. ... The only reason to deploy a modified mdw would be if you added new groups or users. ...
    (microsoft.public.access.security)
  • Re: New to security have questions before plunging
    ... >> you might have new tables, queries, etc and the User Group won't have ... >> permission for these? ... There is no reason to create a new MDW for each ...
    (microsoft.public.access.security)