How so we join an existing workgroup in Access 2007 beta ?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

The security wizard in Access 2007 beta (Database Tools -> Administrator ->
User Level Security Wizard) only permits the creation of a new workgroup
information file (.mdw). It does not seem to permit the joining of an
existing workgroup via an existing workgroup information file.

Is it me or is this an omission from Access 2k7 ?

Kenneth Spencer
 
Security has been removed from 2007, so I doubt there is a Database
Tools-Administrator-User Level Security Wizard.

You cannot 'join' a mdw, but uou can run an existing secured mdb in 2007,
only by using a desktop shortcut that specifies a workgroup file via the
/wrkgrp switch. i.e.
"path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw"
 
Correction on this. You can launch the workgroup administrator via
DoCmd.RunCommand

However, I wouldn't recommend that you make a secure mdw you default by
joining it. Use the desktop shortcut instead.
 
Joan Wild said:
Correction on this. You can launch the workgroup administrator via
DoCmd.RunCommand
Click to expand...

Hi Joan,

I haven't looked at A2k7 at all but have noted the grumblings about security
having been removed - are you saying that security is there but just not
available using conventional "menu" methods?

Regards,
Keith.
 
Lynn and Keith,

If you open up a MDB file in Access 2007 the Ribbon displays a specific chunk with all the typical
security related menu items. Access 2007 will honor the security settings of the workgroup
information file with MDB files and you can make changes as needed.

If you open a ACCDB file (the 2007 file format) in Access 2007 that particular security chunk (and a
replication one as well) simply does not show up on the Ribbon. I believe you can still access some
of the features using DoCmd.RunCommand as Joan noted, but it is in effect useless on an ACCDB file
as Access simply ignores all of those settings. (I haven't fully tested that so I could be off a
bit).

For some security related info with 2007 see this:

http://vb123.blogspot.com/2006/02/access-2007-depreciated-workgroup.html

--
Jeff Conrad
Access Junkie - MVP
http://home.bendbroadband.com/conradsystems/accessjunkie.html
Access 2007 Info: http://www.AccessJunkie.com

in message:
 
Thankyou everyone who replied to my question.
I actually use a bit of VBScript for users to start my Access applications,
so I had already tested Joan's suggestion, and that does indeed work.

I find it a bit odd that we can't join a default Workgroup - surely this
MUST be an omission - otherwise, why have the facility to write security
settings to an MDW file anyway via the Security Wizard ?

If Microsoft are listening, it's not to late to realise the omission and put
it right!

Thanks again,

Ken.
 
The one command that is missing when you open an MDB in Access 2007 is
'Workgroup Administrator', which is the command used in Access 2003 to join
an existing workgroup. There doesn't appear to be any command for this in
the Access 2007 UI, as far as I can see, but you can launch the Workgroup
Administrator dialog programmatically with DoCmd.RunCommand
acCmdWorkgroupAdministrator.
 
Brendan Reynolds said:
The one command that is missing when you open an MDB in Access 2007 is
'Workgroup Administrator', which is the command used in Access 2003 to
join an existing workgroup. There doesn't appear to be any command for
this in the Access 2007 UI, as far as I can see, but you can launch the
Workgroup Administrator dialog programmatically with DoCmd.RunCommand
acCmdWorkgroupAdministrator.
Click to expand...

Thanks for all the info everyone, it'll be interesting to take a look in the
fullness of time - will the Beta version of Office co-exist with 2003
without issue?

Keith.
 
Microsoft advise against installing more than one version of Access, but
many of us do - I'm currently running 2003 and 2007 Beta 2. An alternative
is to use something like Virtual PC. I've used it successfully to run
earlier versions of Access under a virtual installation of Windows 98. The
problem is that later versions of Access require later versions of Windows,
which in turn have higher memory requirements. You need a lot of RAM to
successfully run Office 2003 in a virtual installation of Windows XP.
 
Back
Top