SUMMARY
In SQL 6.5, aliases from a login to a database user could be viewed in Enterprise Manager by double-clicking on that database user. However, SQL 7.0 (or later) Enterprise Manager provides no means to view the logins aliased to a particular database user. This behavior is correct due to the fact that SQL 7.0 and later replace aliases with roles, maintaining aliases only for backward compatibility. All aliases should be dropped, security accounts for the aliased logins should be added to the database, and the security accounts should be assigned to database roles.
For example:
sp_dropalias '<login>;'
go
sp_grantdbaccess '<login>', '<database security account>'
go
sp_addrolemember '<database role>', '<database security account>'
go