Link to home
Start Free TrialLog in
Avatar of NetRat
NetRat

asked on

Migrating Private Views

I am using a script agent to attempt to migrate private views that are stored on the server to another user.  The script  changes the view's 'Readers' field with the other user's name.  After running the script, the view disappears and cannot be seen by anyone.  I have ckecked and double checked that I put the correct spelling of the user's hierarchical name.
Avatar of ghassan99
ghassan99

if u use the script to change back to the original user then it works fine?
Avatar of NetRat

ASKER

Good question... I did try that and it seems that after I change the $Readers field in any way, I cannot recover the view and then no user can see it.  But, here's the weird thing, if I change the $Readers back to the original user, that user cannot view it but an agent that is run using that user's ID can access that private view and modify it.

I must be missing a piece to this puzzle.  What other differences are there between normal and private views?  I have dealt with access fields before and haven't had any problems (weii. the other access fields were all document related though).
Check the security tab of the view, see whose name is listed there before and (if possible) after the change.  Also try to remove the db icon from the desktop and add it again before checking.
Avatar of NetRat

ASKER

I will try what you recommended ghassan.

I will also award points to anyone that can tell me what the programmatic differences are between normal views and private views stored on the server.  It seems like it has to be more than just the $Readers field.
ASKER CERTIFIED SOLUTION
Avatar of ghassan99
ghassan99

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial