|
-
May 27th, 2013, 11:14 AM
#19
Thread Starter
Frenzied Member
Re: Built in Webforms security - Access or Sql Server?
 Originally Posted by gep13
Hello,
Out of the box, the ASP.Net Membership Provider works for a SQL Server Database. There is nothing to stop you from using another database backend though, but you would need to create your own implementation of the Membership Provider, in order to allow the ASP.Net Engine to access the data that you need. Luckily for you, there are many providers out there already, including a Provider for Access.
Here is an MSDN article that talks you through this:
http://msdn.microsoft.com/en-us/libr...v=vs.100).aspx
And this article goes into more detail:
http://www.4guysfromrolla.com/articles/120705-1.aspx
This:
http://www.binarywater.com/OleDbASPN...pProvider.html
seems to be a complete implementation, but I can't say that I have used it.
NOTE: There is a lot of work and configuration involved in setting this up, so unless you REALLY have to, I would suggest that you stick with what comes out of the box.
Thanks, Gary. I'll take a look at this info. Your information - as well as you attitude - has been helpful, as usual.
 I always add to the reputation of those whose posts are helpful, and even occasionally to those whose posts aren't helpful but who obviously put forth a valiant effort. That is, when the system will allow it.
My war with a browser-redirect trojan
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|