There are two ways to create a super link in the Web WebClass HTML that is handed back to the user, and it can be confusing, and I'll explain these two methods in detail:<br>
Method A .<br>
One is to directly use a format similar to this <a href= "xxx.asp?" Wci=sss&wce=ddd "", when this party uses the user to click on this super connection, it will jump to xxx this WebClass SSS purpose sss_userevent event, you can do some processing in this event, and you will And this method of generating a super connection can have a number of custom parameters behind it, such as <br>
<a href= "xxx.asp? Wci=sss&wce=ddd&test=www&me=rrr ... "> The test,me are all our custom parameters, you can use the request (" Test ") method to remove the values in the back of the jump. This provides a way to solve the transfer value of the page;<br>
If you didn't specify WCE parameters, such as <a href= "xxx.asp?" Wci=sss "> then will jump to the Sss_respond event of the XXX WebClass SSS item, not his Sss_userevent event!<br>
Method Two .<br>
The second approach is to use the URLFor method, URLFor (Webitem_name,userevent_value). For example, <a href= "" "& URLFor (Check, CStr (Reccheck (" qtftbn ") ) & "" > "note that there are two dual quotes in place of a dual citation .<br>
This will jump to the Check_userevent event in the check item in this page (which is itself WebClass). The URLFor method only touches userevent events and does not touch respond events! In Check_ In the Userevent event, you can use the EventName parameters of this event to obtain the "CStr" (Reccheck ("qtftbn")), which is the value .<br>
(To continue) <br>
Author: Uestc95 e-mail:uestc95@263.net<br>
