G
Guest
This is more comment than question. I had a problem which I want to document
since I had problems finding this solution. I'd love to hear if anyone else
has alternative solutions or recognizes an error I made somewhere.
The Issue: I am using office developer xp and replication manager 4.0. I
have a replicated database that requires user-level security. User-level
security is set according to the MS Access Security FAQ version 2.41 October
2000. Once user-level security is installed, replication manager will no
longer open the database citing not enough security access is available.
(error 3033).
It seems the problem is that Replication Manager is the default system.mdw.
There is no obvious location to correct this in the program or regedit.
My Solution: In the replication manager start|replication manager shortcut,
change the target (right-click on shortcut, select properties) to read as
follows:
"C:\Program Files\Common Files\Microsoft Shared\Replication Manager
4.0\replman.exe" /wrkgrp "c:\location\filename.mdw"
c:\location\filename.mdw = exact location and filename for the secure
workgroup security file created with Workgroup Administrator during security
setup.
This forces the Replication manager to open the secure workgroup created in
the FAQ protocol. I am now getting a request for username and password from
replication manager, but I can also open and manage the secure database.
I had a very hard time identifying this problem and solution in the
protocols. If anyone sees anything I did wrong, I would love to hear what
else could be wrong. The FAQ reads as if setting up user-level security then
using replication manager should work seamlessly.
since I had problems finding this solution. I'd love to hear if anyone else
has alternative solutions or recognizes an error I made somewhere.
The Issue: I am using office developer xp and replication manager 4.0. I
have a replicated database that requires user-level security. User-level
security is set according to the MS Access Security FAQ version 2.41 October
2000. Once user-level security is installed, replication manager will no
longer open the database citing not enough security access is available.
(error 3033).
It seems the problem is that Replication Manager is the default system.mdw.
There is no obvious location to correct this in the program or regedit.
My Solution: In the replication manager start|replication manager shortcut,
change the target (right-click on shortcut, select properties) to read as
follows:
"C:\Program Files\Common Files\Microsoft Shared\Replication Manager
4.0\replman.exe" /wrkgrp "c:\location\filename.mdw"
c:\location\filename.mdw = exact location and filename for the secure
workgroup security file created with Workgroup Administrator during security
setup.
This forces the Replication manager to open the secure workgroup created in
the FAQ protocol. I am now getting a request for username and password from
replication manager, but I can also open and manage the secure database.
I had a very hard time identifying this problem and solution in the
protocols. If anyone sees anything I did wrong, I would love to hear what
else could be wrong. The FAQ reads as if setting up user-level security then
using replication manager should work seamlessly.