The documentation is asking you not to change authForm.fwx, but rather to make a copy under a different name and use that instead, by changing the value of Auth.AuthFormFile.
The Auth object is part of the main FoxWeb product. You can find out about it by reading the documentation.
Sent by Larry Zhang on 01/26/2006 06:29:49 AM:
Thank you for your reply.
I just feel this kind of checking might be used in many other places. And your documentation said we are not supposed to change anything in your AuthForm.fwx, as it will be overwritten by a new installation. Can I save the change somewhere else and copy it back after installation?
When you say Auth object, where is the object located? Is it a built-in object we can use wherever needed? Sorry, I am really new about this type of thing.
Sent by FoxWeb Support on 01/25/2006 01:32:26 PM:
You could check the value of Request.FormCount("user_id") against the value of Request.Form("user_id"). If Request.FormCount("user_id") is equal to 0, then the user did not submit this field at all (first request?). If on the other hand Request.FormCount("user_id") is > 0 and Request.Form("user_id") is empty, then the user simply submitted an empty user_id.
I would like to re-iterate that you really should be using the Auth object for authentication. You would have to spend weeks of development to re-produce its functionality and robustness.
Sent by Larry Zhang on 01/25/2006 07:38:37 AM:
If user enters his id and password, we check his identity.
If not, we give a prompt. But using these codes, we get the prompt right away, because the field is empty at the very beginning.
We used to put codes in the Valid event of a command button. How to do the same (or similar) in FoxWeb? Thank you.