I see. I think I understand what happened.

Applications in the database are created automatically at run-time. When you run the site like this:

http://localhost

you end up with an app called /

When you browse to it like this:

http://localhost/App1

You end up with an app called /App1

Although the aps are closely related (they belong to the same physical website), they are completely separate from an ASP.NT run-time perspective.

To fix this issue, you can provide an explicit applicationName on the role provider so the same name is used regardless of the way you browse to the site.

About a SQL book: you may want to take a look at Beginning SQL Server Programming: http://www.wrox.com/WileyCDA/WroxTit...764584332.html

I own the Professional 7.0 and 2000 versions of that book and they were great. The Professional 2005 edition is coming out in November, so if you have some background in SQL and some patience, you want to wait for that book...

Cheers,

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004

Thanks for the help. I forgot to thank you for your article on congiuring an ASP.net app to run on IIS with SQL server. Also Scott Guthrie had a helpful post on his blog about the applicationName property.

http://weblogs.asp.net/scottgu/archi...Providers.aspx

Thanks for the follow up. I am sure many others will find this a useful article as well....

Cheers,

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004
Want to be my colleague? Then check out this post.