Continue using workgroups in Access 2007, or something else?

Looking for some insight/suggestions....

Our application has used workgroups for security since it was built in Access 97 many years ago.    Now that we're (finally) migrating to 2007, we're unsure as to whether we should continue using workgroups, or use some other means to secure the accdbs, which link to tables in a Sybase database containing confidential information.

We've gotten the workgroups to work fine in 2007, but we're concerned that workgroups will be de-supported altogether in Access 2010.  

Does anyone have suggestions as to what we could use to secure the accdbs instead of workgroups? I'm reading up on Access 2007 security, but I'm not seeing a clear way to do this.  

Or are we going to be safe, continuing to use workgroups, since they'll still be usable in Access 2010?

Thanks!
L_MalchiodiAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Rey Obrero (Capricorn1)Connect With a Mentor Commented:
see this link

http://office.microsoft.com/en-us/access-help/about-user-level-security-mdb-HP003070410.aspx

and expand

About workgroups and workgroup information files
0
 
Rey Obrero (Capricorn1)Commented:


"You should not convert your database if it relies on user-level security. As with replication, Access 2007 supports user-level security for .mdb databases, but not for .accdb databases. If your database application relies on user-level security to keep certain users from viewing or editing data or from changing the design of objects, or to change the way different users navigate in your application, you need to redesign the application before you convert to the new format."

from this link

Transitioning Your Existing Access Applications to Access 2007

http://msdn.microsoft.com/en-us/library/bb203849.aspx


see this link too
Security Considerations and Guidance for Access 2007
http://msdn.microsoft.com/en-us/library/bb421308.aspx

0
 
L_MalchiodiAuthor Commented:
Thank you....one quick question while I read these links. Will we still be able to leave these databases in Access 2002/2003 format when we migrate to Access 2010?
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
Rey Obrero (Capricorn1)Commented:
yes..the databases in Access 2002/2003 format will still work in A2010
0
 
L_MalchiodiAuthor Commented:
Hm...we're in kind of a bind, then.  We've already converted the databases containing the most code, and done significant development work in them.   We can't really go back at this point.   My mistake.

I think we're stuck with workgroups, then.   From what I'm finding around the web, it looks like they'll still work with 2010.....is that the case?
0
 
Rey Obrero (Capricorn1)Commented:
yes, i believe you can still use the workgroups in A2010
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
To be clear, so long as you have not converted to the .accdb format, your workgroup security will still work.

However, it would seem that you would use the security features of your Sybase database to provide data security. In that case, the only feature that Access ULS would provide would be a "navigation" type of paradigm. If that's all you're using ULS for (i.e. determining which user can open specific Forms, etc) then you can build a system that would mimic this.

The ONLY security feature in 2007/2010 is the database password. This is a much more secure password than older versions but I doubt it would do what you need (and it wouldn't protect your data at all).
0
 
L_MalchiodiAuthor Commented:
Thanks, we're going to stick with the workgroups, as they seem to work well for us with 2007, and provide the security we need.

Now for how to enable them in 2007.  For my own PC, I've done the command in the Immediate window in the Access VBA editor that allows you to bring up the workgroup administrator and join.     Our application is installed on customer PCs with Install Shield.   I understand that what the workgroup administrator is  just setting something in the registry.  Would either of you know what that would be, so we can have our InstallShield package make the necessary registry change?
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
I have no idea what you mean by this:

"I understand that what the workgroup administrator is  just setting something in the registry"

If you mean you want to launch the Workgroup Administrator, then just do this:

DoCmd.RunCommand acCmdWorkgroupAdministrator
0
All Courses

From novice to tech pro — start learning today.