We often face this in Ballet. I am curious to know how others handle it. When people get married they want us to change their tessitura login name (userid) and when they get separated they want to go back to their original login (part of life). It happened couple of times. For now we are managing it by creating a new login. May be in a future version Tessitura can allow us to change the login name, as long as it is unique, by maintaining a separate primary key to refer & link to different other tables without breaking any referential integrity.
Mo
National Ballet of Canada
We haven't had a case of separation yet, but when people get married, a couple of people have asked to change their userid and we've just been up front and said we can't. In my experience nobody's been terribly upset by getting a "no".
We change their email addresses, and generally that's the bigger concern: that communication with the outside world sees their new names. We do change the lname, so any report (or Tstats) that displays the actual name tied to the userid shows their full current names, but the userids stays the same.