Bob,
I could not figure how or where to issue the ALTER LOGIN command.  I
switched the Authentication mode a few times and then read in the help file
that you had to have a strong password. I was not sure what that was either.
Another Help search and I changed my login password to a strong one. A soon
as I did that, I got a message box stating that I needed to stop and restart
the SQL Server service before the change would take effect. Instead of
stopping/restarting service I just re-booted. The moral of the story: If you
don't enter a strong password, it does not work. If you do enter a strong
password, re-boot and all is well.

Bob Hiller

"Bob Barrows [MVP]" <reb01501@NOyahoo.SPAMcom> wrote in message
news:e75SLkcSGHA.4168@tk2msftngp13.phx.gbl...
> Bob and Sharon Hiller wrote: 
>
> Great! 
>
> So you did not have to run the ALTER LOGIN command as shown in the Help
> topic I pointed you to? Interesting ...
> 
> You are now getting out of the realm of ASP and into the realm of SQL
> Server
> Security.  This is a huge topic and you should start in Books Online.  I
> have not started working with SQL2005 yet so any advice I could give you
> may
> be outdated. However, in a nutshell:
> Add the sql logins to the database without assigning them to a global role
> (datareader, datawriter, etc.) in that database.
> Edit the properties of the specific tables to which you wish to grant the
> users access and choose the option/button/page/tab (whatever it is in 2005
> Management Studio) to edit Permissions for the object.
>
> You will get more focussed help in the appropriate sqlserver group ... I
> think there is a microsoft.public.sqlserver.security group, but you should
> check to be sure.
>
> HTH,
> Bob Barrows
>
> --
> Microsoft MVP -- ASP/ASP.NET
> Please reply to the newsgroup. The email account listed in my From
> header is my spam trap, so I don't check it very often. You will get a
> quicker response by posting to the newsgroup.
>
>

[ Post a follow-up to this message ]