TFS and user level rights in .mdb

[BigFoppa]

Hello,
we are using TFS 2005 with Access 2007 thru Developer extensions and TFS
MSSCCI provider. The file format is 2003 as we want to use the old user level
rights. Everything works well except for user level rights. My problem:

When the Access project is under Source Control the menu option for
user/group level rights is not available (dimmed out). The only way to set
access rights on a user or group is to take the project out of source control
(save as to another .mdb file) and open it with the .mdw file as parameter.

Then I delete the old project in TFS and put in the new .mdb thru the Source
Control options in Access. On machine/workspace where this is done everything
seams to work fine. I can do a save as and the user/group settings are still
there.

However, if I on another machine/workspace do a Create from TFS then the
user/group settings are lost.

I know that these things are stored in the system table MSysACEs.
So which way is it: Is the content of this system table not placed in TFS or
is it not retrieved (i.e. placed in the .mdb)?
If it is placed in TFS then is there a way to retrieve it?

PS. I dont know if this is the proper place for the question. If not please
direct me to the proper place. DS.

 

[Paul Shapiro]

Hello,
we are using TFS 2005 with Access 2007 thru Developer extensions and TFS
MSSCCI provider. The file format is 2003 as we want to use the old user
level
rights. Everything works well except for user level rights. My problem:

When the Access project is under Source Control the menu option for
user/group level rights is not available (dimmed out). The only way to set
access rights on a user or group is to take the project out of source
control
(save as to another .mdb file) and open it with the .mdw file as
parameter.

Then I delete the old project in TFS and put in the new .mdb thru the
Source
Control options in Access. On machine/workspace where this is done
everything
seams to work fine. I can do a save as and the user/group settings are
still
there.

However, if I on another machine/workspace do a Create from TFS then the
user/group settings are lost.

I know that these things are stored in the system table MSysACEs.
So which way is it: Is the content of this system table not placed in TFS
or
is it not retrieved (i.e. placed in the .mdb)?
If it is placed in TFS then is there a way to retrieve it?

PS. I dont know if this is the proper place for the question. If not
please
direct me to the proper place. DS.

I'm pretty sure that's one of the limitations of Access' source code control
integration: user-level security is not supported. Check google or Microsoft
documentation to be sure and to find suggested ways to work.

 

[BigFoppa]

I'm pretty sure that's one of the limitations of Access' source code control
integration: user-level security is not supported. Check google or Microsoft
documentation to be sure and to find suggested ways to work.

Well that's what I didn't want to hear. Be sure that I have been searching
for information.

 

[Paul Shapiro]

Well that's what I didn't want to hear. Be sure that I have been
searching
for information.

I couldn't find definitive info for Access 2007, but here is what MS had to
say for earlier versions:

http://technet.microsoft.com/en-us/library/cc723732.aspx#EBAA

Limitations of Source Code Control in Microsoft Access 97
Security
You can't work on user and group permissions when you're working with a
database that's under source code control. The "User and Group Permissions"
menu item is disabled whenever the active database is under source code
control.

To add a secured database to source code control, you must have full
permissions on all the objects in the database. When you add the database to
source code control, the user and group permissions that existed are
stripped away. You need to re-apply your security settings after removing
the database from source code control.

http://msdn.microsoft.com/en-us/library/aa155494(office.10).aspx
Limitations of Source Code Control in Microsoft Access 2000
Security
You cannot work on user and group permissions when you are working with a
database that is under source code control. The User and Group Permissions
command on the Security menu is unavailable when the active database is
under source code control.

To add a secured database to source code control, you must have full
permissions on all objects in the database. When you add a secured database
to source code control, the user and group permissions that existed are
deleted. You need to reapply your security settings after removing the
database from source code control.

 

[BigFoppa]

Paul,

Thanks for making this absolutely clear to me by digging out the information
in the MS archives.

Back to the drawing-board...

/Big