Should we Convert to Access 2007?

[WPW07]

Hello,

We have several complex applications developed in Access 2003 by
various outside consultants. These applications link to a variety of
Oracle tables and are used only for Access reports. User level
security is also built in via the mdw workgroup file for all
applications.

I've been asked to research how viable it is to convert all of these
applications to Access 2007. I understand 2007 discontinued user
level security via the mdw file. On one hand, I see that Microsoft
advises NOT to convert to 2007 if you need user level security:

http://office.microsoft.com/en-us/ac...345611033.aspx

But then it also says that you can use the Workgroup Administrator
Utility in Access 2007:

http://support.microsoft.com/kb/918583

Which is a little confusing.....But the bottom line is we definitely
need to continue with user level security. I'm interested in getting
some feedback and opinions on what we should do. Also, we do not own
SQL Server, but do have MySQL installed.

Thanks for any and all feedback.

[Allen Browne]

Hopefully someone else with Oracle experience will comment too.

As far as Access goes, 2007 has a new file format (ACCDB), and you cannot
use security (MDW) with that. But if you keep your MDB format file and use
it in A2007, you can continue to use Access security. You can fire up the
interface from within A2007 (in an MDB) with this kind of thing:
RunCommand acCmdWorkgroupAdministrator
RunCommand acCmdUserAndGroupAccounts
RunCommand acCmdUserAndGroupPermissions

Other info on converting to A2007:
http://allenbrowne.com/Access2007.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"WPW07" <ww********@gmail.comwrote in message
news:37**********************************@z17g2000 hsg.googlegroups.com...

Hello,

We have several complex applications developed in Access 2003 by
various outside consultants. These applications link to a variety of
Oracle tables and are used only for Access reports. User level
security is also built in via the mdw workgroup file for all
applications.

I've been asked to research how viable it is to convert all of these
applications to Access 2007. I understand 2007 discontinued user
level security via the mdw file. On one hand, I see that Microsoft
advises NOT to convert to 2007 if you need user level security:

http://office.microsoft.com/en-us/ac...345611033.aspx

But then it also says that you can use the Workgroup Administrator
Utility in Access 2007:

http://support.microsoft.com/kb/918583

Which is a little confusing.....But the bottom line is we definitely
need to continue with user level security. I'm interested in getting
some feedback and opinions on what we should do. Also, we do not own
SQL Server, but do have MySQL installed.

Thanks for any and all feedback.

[WPW07]

Thanks Allen.

Just so I understand this correctly....

1. I keep the application in Access 2003. Users who have Access 2007
can open it and create new reports and queries in Access 2007?

2. If an administrator wants to use the MDW file, I should create a
module with RunCommand code?

3. How would I tie the RunCommand code to the MDW file?

4. How would the administrator call it? Should I create a form that
calls the RunCommand code in it?

Thank you,

William

On Feb 27, 7:36 pm, "Allen Browne" <[e-mail]:

Hopefully someone else with Oracle experience will comment too.

As far as Access goes, 2007 has a new file format (ACCDB), and you cannot
use security (MDW) with that. But if you keep your MDB format file and use
it in A2007, you can continue to use Access security. You can fire up the
interface from within A2007 (in an MDB) with this kind of thing:
RunCommand acCmdWorkgroupAdministrator
RunCommand acCmdUserAndGroupAccounts
RunCommand acCmdUserAndGroupPermissions

Other info on converting to A2007:
http://allenbrowne.com/Access2007.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"WPW07" <[e-mail] in message

news:37**********************************@z17g2000 hsg.googlegroups.com...

Hello,

We have several complex applications developed in Access 2003 by
various outside consultants. These applications link to a variety of
Oracle tables and are used only for Access reports. User level
security is also built in via the mdw workgroup file for all
applications.

I've been asked to research how viable it is to convert all of these
applications to Access 2007. I understand 2007 discontinued user
level security via the mdw file. On one hand, I see that Microsoft
advises NOT to convert to 2007 if you need user level security:

http://office.microsoft.com/en-us/ac...345611033.aspx

But then it also says that you can use the Workgroup Administrator
Utility in Access 2007:

http://support.microsoft.com/kb/918583

Which is a little confusing.....But the bottom line is we definitely
need to continue with user level security. I'm interested in getting
some feedback and opinions on what we should do. Also, we do not own
SQL Server, but do have MySQL installed.

Thanks for any and all feedback.

[Allen Browne]

Okay, I generally don't fire the wizards to create a workgroup file in an
end-user database. But I do include the buttons that fire up the
groups/account permissions. For these, you don't need the MDW: it uses the
one that was activated to get in here in the first place.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"WPW07" <ww********@gmail.comwrote in message
news:e5**********************************@o77g2000 hsf.googlegroups.com...

Thanks Allen, do all three of these lines need to be in the module?
Do I need to put in the path and name of the workgroup file? If so
how and where?

RunCommand acCmdWorkgroupAdministrator
RunCommand acCmdUserAndGroupAccounts
RunCommand acCmdUserAndGroupPermissions.

[WPW07]

Does that mean I do need all three RunCommands?
On Feb 28, 9:25 am, "Allen Browne" <[e-mail]:

Okay, I generally don't fire the wizards to create a workgroup file in an
end-user database. But I do include the buttons that fire up the
groups/account permissions. For these, you don't need the MDW: it uses the
one that was activated to get in here in the first place.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"WPW07" <[e-mail] in message

news:e5**********************************@o77g2000 hsf.googlegroups.com...

Thanks Allen, do all three of these lines need to be in the module?
Do I need to put in the path and name of the workgroup file? If so
how and where?

RunCommand acCmdWorkgroupAdministrator
RunCommand acCmdUserAndGroupAccounts
RunCommand acCmdUserAndGroupPermissions.

[Allen Browne]

Can I suggest that you open the Immediate Window (Ctrl+G), and actually try
the commands?

Hopefully you know which ones you will need in your database.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"WPW07" <ww********@gmail.comwrote in message
news:af**********************************@u69g2000 hse.googlegroups.com...

Does that mean I do need all three RunCommands?

RunCommand acCmdWorkgroupAdministrator
RunCommand acCmdUserAndGroupAccounts
RunCommand acCmdUserAndGroupPermissions