checking for duplicate username

[mat]

I'm just playing around and making a register/login script. Before inserting a new user it would be a good idea to check for duplicate usernames so i use:


open DBconnection stuff..

Set dupCheck = connection.Execute("SELECT username FROM users WHERE username = '"&user&"'")
If dupCheck("username") > "" Then
Dim dupU
dupU = True
End If

But i get an error on the line:

If dupCheck("username") > "" Then


I'm not sure what i should be putitng there / checking for? NULL? <>, != etc?

[scroots]

i would go for <> as you want to make sure something does not equal something else.

scroots

[Mhtml]

I would use Len...


if Len(dupU) > 0 Then
'The name exists
Else
'It doesn't
End if

[Roelf]

i believe dupCheck is a recordset, so
If dupCheck.BOF and dupCheck.EOF Then
'no user found
Else
'user found
End If

[Mhtml]

Why use BOF? It will either be at the end or not. Or at the start or not, why not just either of the two?

[Roelf]

thats the way i learned to test for an empty recordset, then bof AND eof is true, if there is a record, they cannot be true both

[Mhtml]

Ok, I see it's just double checking. :)

[Roelf]

if either one of them is true, there can be a record so you have to test for both to be sure there is no record found

[oracleguy]

Wouldn't you only need to check for EOF because if there is no records, it would be at the end of the records and EOF would be true; right?

Thats the way I've always done it.

[mat]

cheers, I was curious about that too :confused:

[whammy]

I agree... I always use:

If NOT rs.EOF Then
' The username exists
Else
' The username doesn't exist
End If

That just seems to make more sense generally, there's no need to check for BOF if you're checking for dupes...

You could do it the other way around too, it doesn't really matter...

If rs.EOF Then
' The username doesn't exist
Else
' The username exists
End If