Re: Connection to a MS SQL Server Table (newbie)
- From: "Jon" <warpedpixel@xxxxxxxxx>
- Date: Wed, 22 Jun 2005 18:51:08 +0100
It does not defeat the purpose (as bob said) because all of the data
contained within an ASP page is not viewable by the user unless directly
written to the page.
You find that HTAccess is worth a look /consideration ... this provides the
ability to set priveleges and groups, etc
--
Jon
warpedpixel@xxxxxxxxx
Look at that dead pixel on your screen! *SLAP* Gotcha!
"Don" <someone@xxxxxxxxxxxxx> wrote in message
news:OxiRVP0dFHA.3184@xxxxxxxxxxxxxxxxxxxxxxx
>I am getting started on a prototype site and have set up one of my home
> machines with IIS and MS SQL Server. Based on several on the posts to
> this
> group, I have been reviewing the ADO connection strings. However, what
> really puzzles me is that it appears you need to use an unsecured SQL
> Server
> (no user name and no password) or provide the username and password in the
> connection string. The latter seems to defeat the purpose of a password.
>
> What I am guessing at this point is that a SQL server account needs to be
> set up with the only the necessary permissions to get the job done. Is
> this
> correct?
>
> In the bigger picture (might be a vision or a hallucination!), this site
> will be a secure site (https://) with username/password access. It is
> basically a departmental personnel database tailored to our specific
> needs.
> The objective is to provide some limiting of access based on groups and
> work
> units (i.e. Group Lead A can only view the people organizationally below
> him).
>
> Any comments, thoughts, references, etc will be greatly appreciated!
>
> Thanks!
>
> Don
>
>
>
.
- References:
- Prev by Date: Re: ASP Admin system pointers
- Next by Date: Re: Test Platform for ASP [newbie]
- Previous by thread: Re: Connection to a MS SQL Server Table (newbie)
- Next by thread: THANKS! -> Re: Connection to a MS SQL Server Table (newbie)
- Index(es):
Relevant Pages
|