Keywords: ASP
Database structure of an electronic greeting card program. (This only represents my personal opinion on a certain period of time). Table Ecard greeting card number ID Auto number field Greeting card Title Title Greeting Author Author Greeting Card's Big Category Catalog1 Greeting Card 2 Category Catalog2 Greeting Card Type CardType is a flash card, or a picture (possibly pictures (possibly the Java card) big picture name Image of course can be Flash or other files, which can include the name of the path small picture Simage
Table ORDER_CARD, used to store a predetermined greeting card. Book a greeting card ID After encoding the KEY big picture of the extraction card, the name of the name of the image template, the name of the template, the name of the template, send card person name Sender send card sendermail Card Name Receiver Career mail Receiver Mailmail Confirm that the CONFIRM mail is used to choose whether to go back (I think this is the least unnecessary, it is better to reply to him) Senddate can choose the date-type data, I think the date is a problem that needs to be taken seriously Especially during the time, I continuously encounter problems in the date format.
The next classification lists the problem with the greeting card, page display, I think all people know more about me. Regarding the implementation of the algorithm of the entire program, I still have some ideas, I don't know if I can simplify operation, please help me see it. 1, the large number of greeting cards and the second level category are preferably stored in another table, generating an automatic number of values stored in the Ecard table, I do this because I think it is to be judged to a field, compare two fields. It is a much faster judgment. Isn't this this in SQL Server I don't understand, I am very obvious in Access. This will be more troublesome when managing the greeting card, but the number of times is not a lot. 2, do not take the page from the library, you can work well with your hand, and better ways to use the program. All kinds of paging display, the specific greeting card page can be generated by the program, or you can use the ASP dynamic from the library. At the front end time I am fanatized in a static page, generate a static page and a chain page, but there have been some problems, to generate some dynamic pages in the static page The effort is much larger. At the same time, due to the complexity of the program, the page generation is not automatically automatically, becomes many times to stop the work of the hand to update the greeting card page, and doing so the complexity of the system is high, maybe you will say this is not difficult, but I think If another person takes over this job, if you want to migrate the server, the work involved will become more. From this, I got a conclusion, if you are not full of this greeting card program, or dedicated to a few jobs, if you don't work a full-time greeting card website, I think the dynamic page is a better choice, of course if you have Better algorithm to achieve that otherwise followed. 3, if you use the dynamic page, when all greetings are displayed, you can include parameters such as template, image, such as only one ID value, because the page with the greeting card information is specifically displayed. Show a specific greeting card without operating the database again. 4, here we use WSH to implement timeline card function, as for how to use WSH to issue we specialize in another chapter. 5. Due to the use of WSH to implement a timing issuer, we can cooperate with Jmail or any other letter to send the HTML format, unless SQL Mail can only send a file format. In HTML format we can embed JavaScript
