Primary Key Violation

[James]

Hello,

I have a database that has a primary key for username.
I'm using an ASP page to allow people to register on line,
I have username set as primary key. When they try to
click to add theirselves to the db through the ASP page,
they receive an error - primary key violation. Is there a
friendly way to tell them they cannot add their record
because a username already exist before the SQL Server
message occurs?

James

[Aaron [SQL Server MVP]]

[url]http://www.aspfaq.com/2509[/url]

--
[url]http://www.aspfaq.com/[/url]
(Reverse address to reply.)




"James" <anonymous@discussions.microsoft.com> wrote in message
news:1ff5201c45897$393b9a90$a501280a@phx.gbl...

> Hello,
>
> I have a database that has a primary key for username.
> I'm using an ASP page to allow people to register on line,
> I have username set as primary key. When they try to
> click to add theirselves to the db through the ASP page,
> they receive an error - primary key violation. Is there a
> friendly way to tell them they cannot add their record
> because a username already exist before the SQL Server
> message occurs?
>
> James

[Evertjan.]

James wrote on 22 jun 2004 in microsoft.public.inetserver.asp.db:

> I have a database that has a primary key for username.
> I'm using an ASP page to allow people to register on line,
> I have username set as primary key. When they try to
> click to add theirselves to the db through the ASP page,
> they receive an error - primary key violation. Is there a
> friendly way to tell them they cannot add their record
> because a username already exist before the SQL Server
> message occurs?
>

sql="select ... where username = " & request.form("username")
mDATA=cnct.execute(sql)
if not mDATA.eof then response.write "you are known already"

--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)