Hi Alberto,
if you choose a number as your usu:id field, then yes the user could change the url to be another number. But so what? What can the form do that would be malicious to another user?
the first line of attack would be to make the userId say a random 16 character string. Or at the very least a random number, not an auto-incremented number. Trivial to do and either would have a useful effect.
Or, make a new memory table - and in it have a "user id" field, and a (randomly generated) index field. Use the index field in the URL, then on the server map it to the User ID field.
But yes, there's another way.
Simply don't use a form. Use a NetWebPage. Then code the specific functionality you like onto the page. In this case "read user from file, set allowed to 1, write record away". Since this is all the page can do there's no need for the Change button parameter, and the user can't do anything malicious.
TIP: Outlook requires that the text displayed be the whole link and nothing but the link or it will suppress it. This is an anti-fishing measure. So your link cannot have alternate text "eg Click here to finish your registration". It must show the user the complete, and whole, URL.
Cheers
Bruce