I never use the DotNetNuke package's included App_Data/Database.mdf file even though I uses MS SQL Express 2005 and 2008 for development. Instead I prefer to create a blank database using SSMS for each DotNetNuke installation and when setting up the connection strings in the Install Wizard or web.config treat the Express database server as a full MS SQL 2005 or 2008 database server. This not only avoids the issue to which you refer not only allowing me to work with the database outside of DotNetNuke (with SSMS or VS) when creating custom tables, sprocs, etc. but also makes it easier to create a database backup for migration to another server.

For more information on the issue of attaching to the user instance database outside of DNN and the effect that this will have on your web.config connection strings, please see this blog post from Shawn Mehaffie:

http://www.dotnetnuke.com/Community/B...

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner