During development (VS2005) I have my connection strings set up to use Windows Authentication. Everything works fine within VS. However, when I publish to production everything breaks. First, I get SQLExpress login errors for the <DOMAIN>\ASPNET user. So, I add that user to the database (so much for Integrated Security) and everything is kosher (of course, I had to modify folder permissions, as well). Once I got access resolved for ASPNETDB then I started having problems accessing a separate database file - no data is being returned. So, I decided to try connecting to that database from within VS. Unfortunately, it won't connect from there anymore with Windows Authentication. So, I have to add yet another login for my own account so I can access that database from within the development environment. Before publishing the next time I follow some advice from this forum and remove the connections to each database from the VS project before I do the build/publish. I get some new errors and decide to reconnect in SQL Express Management Studio to check permissions. Oops, cannot connect to those files any more because the login "default database" cannot be connected. I end up having to create a new adminstrator user on my computer so I can crank up the management studio and delete those logins so I can start using the database again from VS. Now I can connect again in development but nothing works AGAIN in production. I'm rapidly becoming frustrated with VS2005 and SQLExpress, at least as far as web development goes.