Solved

Password defined as SQL_Latin1_General_CP1_CS_AS but not being recognized when entered

Posted on 2014-04-04
10
220 Views
Last Modified: 2014-04-15
A table has been created that has two fields (i.e., UserId, UserPswd) defined to be SQL_Latin1_General_CP1_CS_AS.

When I enter the user id that is not in its proper case, my program issues the correct message indicating that the user id is not correct.

However, when I enter the user password that is not in its proper case, the program accepts the password as being correct.

Can someone tell me why the SQL_Latin1_General_CP1_CS_AS works for one field but not for the other?  Do I need to do something else to get it to be recognized.

Thank you.
0
Comment
Question by:CarmenMTorres
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
  • 2
10 Comments
 
LVL 53

Expert Comment

by:Scott Fell, EE MVE
ID: 39979773
Is this for your code?  Are you sure you don't have code that converts the password to all upper or lower case or ignores case?
0
 

Author Comment

by:CarmenMTorres
ID: 39980687
The passwords are encrypted, but when accessing or reading the passwords, they are decrypted.
0
 
LVL 75

Expert Comment

by:Anthony Perkins
ID: 39981938
Please post the schema for your table.
0
Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

 

Author Comment

by:CarmenMTorres
ID: 39986130
I was able to determine the issue.  I needed to append the clause "COLLATE SQL_Latin1_General_CP1_CS_AS " to the password after it was decrypted.  Once I appended the clause, the function was performing properly.

Thank you all for your input.
0
 

Accepted Solution

by:
CarmenMTorres earned 0 total points
ID: 39991364
Since I was able to resolve this issue myself by appending the clause "COLLATE SQL_Latin1_General_CP1_CS_AS " to my query statement , Administrator can you please close this question.  Thank you.
0
 
LVL 53

Expert Comment

by:Scott Fell, EE MVE
ID: 39991445
Just accept your own answer.
0
 
LVL 75

Expert Comment

by:Anthony Perkins
ID: 39991632
0
 
LVL 53

Expert Comment

by:Scott Fell, EE MVE
ID: 39991676
On that comment, click "Accept as Solution". You will be redirected to the Award Points and Grade page for your question.
0
 

Author Closing Comment

by:CarmenMTorres
ID: 40001125
I was able to determine the answer to my problem before a solution was suggested by the experts.
0

Featured Post

Moving data to the cloud? Find out if you’re ready

Before moving to the cloud, it is important to carefully define your db needs, plan for the migration & understand prod. environment. This wp explains how to define what you need from a cloud provider, plan for the migration & what putting a cloud solution into practice entails.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

It’s a strangely common occurrence that when you send someone their login details for a system, they can’t get in. This article will help you understand why it happens, and what you can do about it.
This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
Viewers will learn how to use the SELECT statement in SQL and will be exposed to the many uses the SELECT statement has.

632 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question