Thanks for the compliment TSG. Not sure how they can do this, as the dynamic SQL that SQL Server 2000 Enterprise Manager kicks off to get the database details is as follows:

select name,

 DATABASEPROPERTY(name, N'IsDetached'),    

 (case when DATABASEPROPERTY(name, N'IsShutdown') is null then -1 else DATABASEPROPERTY(name, N'IsShutdown') end),    

 DATABASEPROPERTY(name, N'IsSuspect'),

 DATABASEPROPERTY(name, N'IsOffline'),    

 DATABASEPROPERTY(name, N'IsInLoad'),    

 (case when DATABASEPROPERTY(name, N'IsInRecovery') is null then -1 else DATABASEPROPERTY(name, N'IsInRecovery') end),    

 (case when DATABASEPROPERTY(name, N'IsNotRecovered') is null then -1 else DATABASEPROPERTY(name, N'IsNotRecovered') end),    

 DATABASEPROPERTY(name, N'IsEmergencyMode'),

 DATABASEPROPERTY(name, N'IsInStandBy'), has_dbaccess(name),    

 status,

 category,

 status2

from  master.dbo.sysdatabases

I'd be very interested to know how they could restrict the information that is brought back to just those rows which the currently connected user is entitled to see. Great idea though, would be very useful in locking down the environment further, will try to find out if anything like this has been included in SQL Server 2005.