Recommended: Internal discussion on handling ASP requests ASP requests are initialized by WAM objects. The WAM object then sends it to ASP-RunTime. ASP-RunTime responds to it by creating an internal page object. A WAM object is a free thread object. When it calls an ISAPI extension such as ASP.DLL, it
In almost every site, we have to use programs to output lists: news lists, product lists, etc. The output method also varies depending on the content. For news lists, it is usually a circular output of row by row; for product lists, it is usually a cell-by-cell output. Below we will use ASP to output a table with five elements and four columns.
1. Line-by-line output
| The following is the quoted content: <% Response.Write(<table border=1 width=200>) For i=1 to 5 Response.Write(<tr><td> </td><td> </td><td> </td><td> </td><td> </td></tr>) Next Response.Write(</table>) %> |
There is nothing to say about this, everyone can understand it.
2. One cell, one cell output
| The following is the quoted content: <% Response.Write(<table border=1 width=200>) For i=1 to 18 If i mod 4 = 1 Then Response.Write(<tr>) Response.Write(<td> </td>) If i mod 4 = 0 Then Response.Write(</tr>) Next 'Fill in the cell i = i - 1 If i mod 4<>0 Then For j=1 to 4-i mod 4 Response.Write(<td>replenishment</td>) Next Response.Write(</tr>) End If Response.Write(</table>) %> |
Here we need to explain: many ASPs that output N rows and N lists on the Internet do not consider whether the number of columns in the last row is complete, that is, there is no supplementary part above, and a broken table is output. Although there are not many problems in details, I hope everyone will pay attention to it.
Share: ASP error collection ASP error collection is helpful to beginners, and perhaps experts will forget it. ASP error collection Microsoft VBScript language*Error (0x800A03E9)-->Insufficient memory Microsoft VBScript language*Error (0x800A03EA)-->Speech*Error Microsoft VBScript language*Error (0x800A03EA)-->Speech*Error Microsoft VBScript language*