Hi there,
If the Server Behavior doesn't support it, you'll need to write some code yourself. Here's what you could do:
1. Right before the Update Behavior executes the UPDATE statement, write some SQL that looks for the current user. E.g.:
sql = "SELECT COUNT(*) FROM YourUsersTable WHERE Name = '" & userName & "'"
Set rsCheck = yourConnection.Execute(sql)
If rsCheck.Fields(0).Value = 0 Then
userFound = False
Else
userFound = True
End If
rsCheck.Close()
2. From here, you can use the userFound variable to determine what to do next, like allow the update or redirect to another page.
Alternatively, you can also use the existing Check New Username behavior and adapt it to fit your scenario. This will probably break the behavior in the Behaviors panel, but you can at least reuse the code.
Finally, you can avoid the problem altogether by prohibiting users from changing their user name. Usually, after you sign up, this name can no longer be changed (for example, I can't change my user name here at the Wrox site, other than maybe sending an e-mail to the Administrator).
Regarding your personal message: this forum is not "devoid of activity". It's not very busy because it's about old books, but whenever you post here, you usually get an answer.
Hope this helps.
Imar
---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of
ASP.NET 2.0 Instant Results and
Beginning Dreamweaver MX / MX 2004
Update Record/Check New Username
