I satisfy this requirement by returning a set via a stored procedure
and then building a simple asp.net grid with the results.
It dosen't give last update but it does give last connection
The base assumption is that if a resource dosen't
connect they can't update.
Here is what I use for 2003
CREATE PROCEDURE dbo.ab_GET_PWA_last_login
AS
SELECT
RES_NAME as resource,
WRES_LAST_CONNECT as lastconnected,
DATEDIFF(dd, WRES_LAST_CONNECT, GETDATE()) as daysago,
GETDATE() as runtime
FROM MSP_WEB_RESOURCES
WHERE WRES_NT_ACCOUNT IN
(
'Domain\username1',
'Domain\username2',
......)
OR
RES_NAME IN
(
'PWAuthentication1'
......
)
I actually started writing this and similar sets to an audit table
on a daily basis via an sql job. I can examine over history
who in the organization are not even visiting PWA and therefore
probably under reporting.
Both IN statements can be set up as lists or dynamic Selects
to filter the audit as needed.