How to call last saved data from sql server in visual studio

Question

1.00/5 (1 vote)

See more:

VS2010

Dear Coders,

Please help me get the last saved data from a table in a textbox so that i can compare it is unique. I know setting primary key will do this but in the user end i would like to show this. Like when when we enter a e-mail id for registering in a website it will show like "Email I.D Already Exists"

Hardly waiting for the reply.. Please help.

Posted 1-Nov-12 3:54am

armarzook

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

fjdiewornncalwe · Answer 1 · 2012-11-01T04:46:00

You have a few different options on doing validation like this.
1) If using a stored procedure, you can let the procedure query the table before insert to validate that the new value is unique. If it is not, you can throw an exception back to the application indicating that the item already exists.
2) If you are using a direct query, then you will receive an exception back from the execution of the query if you have proper primary and unique constraints set up on your table.
3) This option is possible, but NOT the one I would choose as it requires extra calls to the database. You could also query the table in question from your application for a record matching the new entry before attempting to insert. If the record exists, you can deal with it the. If the record does not exist, then you insert it.
Cheers.