Groups | Blog | Home
all groups > visual studio .net general > november 2006 >

visual studio .net general : Access Databases and ASP.NET 2.0


Rodger Barnett
11/19/2006 2:18:01 PM
I am sure that this is a simple (but annoying problem)

I want to be able to use an Access (2003/2000) database to control
membership, login as well as the underlying site data.

I appreciate that using this database rather than a SQL Server Express or
SQL server database is less robust. However the volume of data and traffic
that I anticipate for this is low AND as a result the additional cost of
hosting a SQLServer database cannot be justified.

I cannot set up a new website to use an Access Database to hold the site
management data.

The The provider tab on the ASP.NET configuration tool says

Use this page to configure how Web site management data such as membership
is stored. You can use a single provider for all the management data for your
site or you can specify a different provider for each feature.

[b]Your application is currently configured to use the provider:
AspNetSqlProvider[/b]

and does not give any other choice to change

The Security Tab of the ASP.NET configuration tool for a prebuilt sample web
application says

[i]You can use the Web Site Administration Tool to manage all the security
settings for your application. You can set up users and passwords
(authentication), create roles (groups of users), and create permissions
(rules for controlling access to parts of your application).

[b]By default, user information is stored in a Microsoft SQL Server Express
database in the Data folder of your Web site. If you want to store user
information in a different database, use the Provider tab to select a
different provider.[/b] [/i]

...again I don't have (or appear to have a way to change this)

Help appreciated

William Sullivan
11/20/2006 6:23:02 AM
I can't answer your question, but I can say that Sql Server Express is free
to use, and can handle much more traffic than any access database can.
Essentially, you just have to print out the eula, read it, keep a copy of it,
and sign an agreement stating you won't break the eula (which isn't that
offensive, when you read it). Check it out:
http://go.microsoft.com/fwlink/?LinkId=64062. I believe that the license
agreement prevents you from renting an instance of Sql Server Express, so if
a hosting company allows you to use it, and then charge you for it, they are
in violation of the eula. If that's the case, bail on them, as they won't be
around for the long run.

As for the default provider, its set in the base directory of IIS or in your
machine configuration. I'm not exactly sure where it is; but in your
website you can ditch it by adding a <remove> tag in your providers section
of web.config to remove that membership provider, then add a new one, or
re-add it but this time as a custom provider.

I've messed with creating a custom provider, and I can tell you that it
isn't fun. Avoid if at all possible.

[quoted text, click to view]
AddThis Social Bookmark Button