russellhltn wrote:To me, the ideal method is to merge the two users. But I don't know as there's anything that can be done on the MLS end. Perhaps LUS has a trick up their sleeve.
I doubt that LUS has any capabilities for this, short of capturing the database, making changes directly to the db tables, and sending it back. That's more hassle than this is worth.
russellhltn wrote:While associating it with another user would work, that bothers me. In the event of an investigation, it records the transactions as being done by the wrong person. A small likelihood of happening, but it's not impossible.
Although it's conceivable, it's extremely unlikely. Remember that MLS started checking for duplicate MRNs with MLS 3.3, which was released in December 2010. So no duplicate users have been created since then. Thus it's quite likely that any duplicate deactivated account is dealing with transactions which (at least for the US with its 3 year retention period) are in the very oldest year. Of course, it's possible that both of the duplicated accounts continued to be used after 3.3 came out, but that's even more unlikely.
Furthermore, the transactions are connected to the user, not the person (although clearly they are indirectly connected to the person through the user). I'm not proposing anything that would change that linkage.
Short of dumping the problem on LUS, my proposal seems like the only self-service option that would work.