Thanks for the info!

I've played around with application roles, but we had to ditch that when we found out that you can't access another database once you've set the application role, and that functionnality was required. I guess we could have opened up another connection, though!

>Yep, that's what we do ... We use a single user log-in to the database, and then assign a role to the Application ... that enables our app to optionally use a table-based security. I'm no SQL Server expert, so if you don't know about Roles, you'll have to look it up cuz I don't think I can explain it (or maybe someone else can jump in here ...)