OK,

Finally getting around to asking about hitting a SQLExpress DB from a Visual Web Developer App on Vista.

Typical sample connection strings are like:

<add name="AppConnectionString1" connectionString="Data Source=&quot;.\SQLEXPRESS&quot;;AttachDbFilename=& quot;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\AdventureWorksLT_Data.md f&quot;;Integrated Security=True"
        providerName="System.Data.SqlClient" />

No dice.


Moved the AdventureWorksLT_Data.mdf file to C:\Users\Public, attached it to my SQLExpress instance through Management Studio and tried to hit it with:

<add name="AppConnectionString1" connectionString="Data Source=&quot;.\SQLEXPRESS&quot;;Initial Catalog=&quot;AdventureWorks_Data.mdf&quot;;Integr ated Security=True"
        providerName="System.Data.SqlClient" />


No dice.

Aslo tried leaving AdventureWorks_Data.mdf in C:\Users\Public without attching it to SQLExpress and using AttachDbFilename=&quot;C:\Users\Public\AdventureWo rksLT_Data.mdf

No dice.

Anybody have the secret. I don't want to use the App_Data file (as in AttachDBFilename=|DataDirectory|), but hit the DB after it has been attached to SQLExpress. I suspect UAC is mucking things up again, just don't know how to get around it.

Thanks,

Bob

NEVER MIND!!! SORRY!!!

The sample app I was trying to run kept redirecting me to a page indicating that the DB couldn't be found when that wasn't the actual problem.

Got it all running OK.

:)