I have a 145mb database that went through massive changes. Having users replicate these changes is not feasable. I was hoping to be able to make a replica using my ID, and then burn this to a CD… I did what I was supposed to > reindexed the views before burning the CD > made sure the replica was made without encryption (R6 got me on this earlier in the week)…
But my users are getting the “not authorized” error when trying to bookmark or open the database.
Do I have to use each individual ID and make a replica under their name?
It doesn’t make sense to me > I know that there are large shops out there that have to deploy large databases to many users. How is this done?
Not positive on this, but depending on how your ACL is setup, I think if you have the database Enforce consistent ACL across all replicas, then other users won’t be able to open a local replica.
Yeah, I think that could have somehting to do with it, if the users’ access is controlled by groups. E.g. say the default is “No Access” and the users have access via a group called “HugeApp Users”. If the replica has consistent access control, the Notes client has no way to know whether the current user is a member of HugeApp Users group. To be on the safe side, it denies access. When the user replicates the application, their Notes client should – I hope – get the information that they’re a member of the group, and expand their access.