Hi,

thank you for the quick reply.

I don't think this would work since:

> new sql server and master or msdb have not clue about the mdf

> the mdf was ungracefully shutdown...

Here is the situation:

> C drive containing the SQL server 2005 is gone

> D drive for data is available

> E drive for logs is GONE

> no backup of mdf nor...

I agree, this would defnitely do the task..

if you don't wish to have multiple DSN or the odbc connections to your Access program then you may want to kick this tire;

> create a single odbc on...

this is very cool... although, it shows the db_user and if this is a role and if you have multiple users in that role it could get couldy pretty quick...

2007-11-30...

I believe logins can be mapped to the DB, but, it is the DB / security / users that has the user mapping / securables. At that point you may...

> use AD accounts

> use AD security groups

> turn off public / guest accounts and groups (minimize access if can't remove)

> use change mangement control and log the sql...

I could be wrong, but, I don't think this would tell you who did it though, if that was original question's intention..

I like this script, I think I might use...