Re: Connection to SQL Server
- From: "Brendan Green" <bgreen@xxxxxxxxxxxxx>
- Date: Tue, 24 May 2005 09:32:46 +1000
Well, HTTP is a stateless protocol, meaning that each subsequent page
request does not know anything about any prior requests.
What you need to do is establish a connection to the SQL server on each page
request.
"rodneybauer1" <rodneybauer1@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:157A5750-910B-4A5F-A06D-A17E3858C79E@xxxxxxxxxxxxxxxx
> I'm just learning this stuff, but I recall reading about "session state"
> and
> "view state" being able to deal with what you want to do. the msdn library
> should have samples
>
> "Graeme" wrote:
>
>> I want to have an ASP.Net application to connect to a SQL Server
>> database.
>>
>> I can't use Active Directories or Windows authentication (network
>> security!). So I want to use Forms authentication to allow the user to
>> enter
>> their SQL Server username and password, check their permissions (from a
>> table), and then add them to a SQL Server Application Role. I want to
>> use
>> the SQL Server Application role to simplify the management of permissions
>> with SQL Server.
>>
>> I can set up the authentication in the dotnet application.
>> I can access the user passwords.
>> I can run the sp_addapprole stored procedure to add a user to the
>> application role.
>>
>> But I can't maintain the connection to SQL Server (and application role)
>> when I change pages within the application.
>>
>> Any suggestions?
.
- References:
- Connection to SQL Server
- From: Graeme
- RE: Connection to SQL Server
- From: rodneybauer1
- Connection to SQL Server
- Prev by Date: Re: Windows Forms MainMenu question
- Next by Date: Re: streamwriter working in windows but not web...?why?
- Previous by thread: RE: Connection to SQL Server
- Next by thread: Re: Connection to SQL Server
- Index(es):
Relevant Pages
|
