Design the receiving and publishing management system with ASP (2)

Related implementation technologies
1. Design of typical data tables
In the receiving and publishing management system, any receiving or publishing File corresponds to a default process (defined in advance), and the file is transferred down one by one according to the steps specified in the process. Take an email receiving process as an example: email receiving registration-> proposed by the director-> approved by the leadership-> hosted by the office-> archive the application. In order to track files in real time, monitor their flow processes in a timely manner, or investigate the handling details in some stages, we need to provide two important data tables, in this system, the data tables are gw_mrlc and gw_cllc.
Gw_mrlc (wdlx, lcmc, ry, xh, clm, clr) records information about the default processes used in the system. Wdlx refers to the document type, receiving or publishing documents; lcmc refers to the process name; ry refers to the person who defines the default process; xh corresponds to the sequence number of each step in the default process, which has different sizes, if it is small, it indicates that the step is in the first place. clm indicates the name of each step in the default process, and clr indicates the handler of each step in the default process.
Gw_mrlc only records the information of each process and also needs gw_cllc (lxh, lcmc, xh, clr, jbrq, clrq, clyj, zt, wjm) to track the execution of files in the process. Each unique process corresponds to one of the processes in the system. lxh records the serial number of the process. The serial numbers are defined as above in lcmc, xh, and clr. jbrq, clrq, clyj, zt, and wjm are all for each processing step in the process with the serial number xh, jbrq refers to the date when the processing of the previous step is submitted; clrq refers to the date when the processing of the current step is completed; clyj refers to the processing opinion of the current step; zt refers to the processing status of the current step, which has been processed or not yet processed, so as to facilitate real-time file tracking; wjm records the body content of the file and the modification traces of the file during the transfer process, which can be implemented through the file upload function.
2. Use Session for logon verification
ASP code uses forms for interaction, and the corresponding content is reflected in the address bar of the browser. If appropriate security measures are not used, you only need to write down the content, you can directly access a page without authentication. For example, in the browser, enter "... xx. asp? Flag = 1 ", you can directly enter the page that meets the" flag = 1 "condition without going through the form page.
To prevent unregistered users from directly accessing the application system through the registration interface, we use the Session object for registration verification. For example, we have created the following registration page.
<% 'Read User login information
Luser = ltrim (Request ("User "))
Lpass = Request ("Pass ")
'Check whether the account and password are correct
If Luser = rs ("userid") and Lpass = rs ("password") then
Session ("sysuser") = Luser 'use the Session object for user login verification
...
Else
Response. write "Your input is incorrect !"
Response. end
End if