login case senssitive

I would like to have a login page that is case senssitive. Right now the userName field in DB store Example :"John", but it allow the user to log in even if he types "john". Is the any SQL statement that select only if if name match and the case are match?::Is the any SQL statement that select only if if name match and the case are match?

=

I assume you use "Like". "Like" ignores case.

Now- otos - does your request make sense? I mean

::I would like to have a login page that is case senssitive. Right now the userName field in
::DB store Example :"John",

If "John" and "john" are different users, you open pandora's box for people mixing this up.

Our security systems ware case insensitive and store - besides the "DisplayName" also a "UniqueName" (name in lower cases), which triggers a unique constraint.

Having two users that differentiate their name only by casing sounds to me like a terrific bad idea. I can imagine the support calls coming in.|||The reason for case sensitive is because later on in my application i am using the user name and it has to be at certain form.
my select statement is:
"SELECT* FROM[FrenchRoast].[shikozel_db].[Chef] WHERE (([Chef].[Name] = @.Name) AND ([Chef].[Password] = @.password))"

I dont use like.
thank you.help...|||::The reason for case sensitive is because later on in my application i am using the user
::name and it has to be at certain form.

With all respect, this is no rason to make logins case sensitive. All my arguments are true - you willget into trouble with people spelling their name wrong when logging in.

Btw - if this:

::AND ([Chef].[Password] = @.password))"

indicates that you store the password in clear text in the database, then PLEASE get an introduction book on security. Storing the paswords in the database opens you up for a lot of not-funny things, including a tremendous amount of legal liability in case something does go wrong - without any legal defence, as it is gross neglect. Passwords should never ever be stored in the database.|||thank you for your comment. Where should i store passwords? any tutorial or books?|||::Where should i store passwords?

You should never ever store passwords. Look at how modern operating systems do it - they also never store passwords.|||Thona is correct, case sensitive passwords are a bad design and clear text pw's are equally as bad from a security stand point, so I recommend you read up on MD5.

Logic in format?

Hello,
This might be a simple questions for you guys.
Can you put logic withing the format of each cell; for example if i have a
number column and i want all numbers > 0 to be red and numbers<=0 to be blue.
Can this be done?
Thanks.Click on your field and go to properties box Go to properties box. Find color
property and and in the drop down box select <expression>. Use an IIF clause
in place of black. IE:
=IIF(Fields!fieldname.value <= 0,"Blue","Red")
"Ash" wrote:
> Hello,
> This might be a simple questions for you guys.
> Can you put logic withing the format of each cell; for example if i have a
> number column and i want all numbers > 0 to be red and numbers<=0 to be blue.
> Can this be done?
> Thanks.|||Actually you can code for most of the field properties. If your report is
going to be printed and you only have a black laser, changing the font to
bold makes it stand out. I had this issue come up earlier today.|||Do you do that in the one click report builder (that you can launch from the
web) or from within the VS2005 editor?
because i tried it from the report builder and when i right click a field i
get 'Format', 'Edit Formula' and 'Delete' only.
I think i'm missing somthing..
"William" wrote:
> Actually you can code for most of the field properties. If your report is
> going to be printed and you only have a black laser, changing the font to
> bold makes it stand out. I had this issue come up earlier today.|||I was describing the process in RS designing in the MSDE designer within VS
.Net 2003. I know there is a Report Builder in 2005, but I have not tried
it yet.