|  |     Steve. 
    In your scenario, the more common question is 'what happens if user B is
    transferred' - the shared files are moved to the Holding Account 
    (policies) when the old account is deleted.
    
    But if user A moves, then I think the pointers will remain until the
    first housekeeping run of FCVR, when I suppose they would be tidied up?
    I haven't checked this, though... perhaps someone more familiar with
    this will correct me?
    Cheers
    DaveT
 | 
|  | I'm sure we try to be awfully clever about this and update all the pointers so
that they still point to user B's drawer (which if user B was remote to user A
before the transfer becomes a no-op anyway?)?
Of course, you'd need to set up appropriate proxies to allow access, but the
pointers should all be there.
He said na�vely...
Scott
 | 
|  |     Hi there!
    
    	Yes, it is a bit of a dog's breakfast isn't it? :-)
    
    	I have just checked the code, and I can say with some degree of
    	certainty that transfer user does not change shared drawer
    	references during the transfer. That means if you had
    	FOO::"[BAR]SHARE" in your filecab before the transfer, then the new
    	account on the new machine should still have the pointer to that
    	drawer, which could still be valid.
    
    	However, there seems to be a flaw in this logic in that local
    	shared drawer references will be 0::"[BAR]SHARE" and will be
    	incorrect on the remote machine. I suspect this to be a bug, as
    	this code predates the 0:: convention -> in the beginning the
    	nodename was stored in FILECAB.DAT even for local drawers.
    
    Regards,
    Paul
 |