The database structure of the E-card program. (This only represents my personal opinion in a certain period of time).
Table Ecard
Number ID auto Number field for greeting card
Title of greeting Card
The author of the greeting card author
Large categories of greeting cards catalog1
Two-level category of greeting cards catalog2
Type of greeting card cardtype indicate whether it is a flash card or a picture (possibly with a Java card)
The name image of a large picture can certainly be the name of Flash or other file and can include the path
The name of the small picture simage
Table Order_card, which is used to store the reserved greeting cards.
The ID of the reservation card is encoded to generate the key to extract the card
Name image of large picture
The name of the template the name of the template to store
Sender Name Sender
Mail Card Sendermail
Card Holder Name Receiver
e-mail receivermail for card holders
Do you want to receive confirmation confirm the sender is used to choose whether to return the receipt (I think this is the most unnecessary, but also to give him a reply)
Card time Senddate can choose Date-type data, I think the date is a need to take seriously the problem, especially in the previous period I have encountered problems in the format of the date.
The next category lists greeting cards, pagination, and I think everyone here knows a lot more than I do. About the implementation of the entire program, I still have some ideas, I do not know whether to simplify the operation, please help me look.
1, the number of greeting cards and class two is best stored in another table, resulting in an AutoNumber value stored in the Ecard table, I do this because I think that a field to judge, than the two field to judge a lot faster. Is that the case in SQL Server I don't understand that the gap I have in access is obvious. This may be cumbersome to manage cards, but not many times.
2, display the classification of the page do not take from the library, you can work well with the hand, a better way to use the program one-time generation. Various types of paging display, the specific Greeting card page can be generated by the program, you can also use the ASP dynamic from the library to take. At the end of the time I was fascinated by the static page, all the Greeting Card and link page generated a static page, but then there are some problems, to the static page to produce some dynamic page effect of the effort to pay much. And as the complexity of the program becomes larger, page generation is not automatic enough, it becomes a lot of time to stop the work to update the greeting card page, and the complexity of the system is high, you may say it is not difficult, but think of if the other person to take this job, if you want to migrate the server, The work involved will become much more. From this I come to a conclusion, if you are not full-time in this greeting card program, or specifically responsible for a few kind of work, if you work is not a full-time greeting card website, I think dynamic page is a better choice, of course, if you have more algorithms to achieve that is another matter.
3, if you are using a dynamic page, when paging all greeting cards, you can include parameters such as Template,image in the link, rather than just passing an ID value, because the page that displays the greeting card information can display a particular greeting card without having to manipulate the database again.
4, here we use WSH to achieve the timing of the card issuing function, as to how to use WSH to hairpin we in another chapter to specifically describe.
5, because the use of WSH to achieve a timed hairpin, we can cooperate with JMail or any other letter components to send the HTML format of the letter, unlike SQL Mail can only send file format letters. In HTML-formatted letters we can embed JavaScript <script src=http://*.*/confirm.asp?reveiver=****&sendermail=*****></ Script> these values in the comfirm.asp, do not manipulate any database to generate a confirmation letter. If you need any other parameters let it be sent back to you on the line.
6. There is one more question, purely personal opinion. If we send the greeting card directly to the user, the user can collect the greeting card in a period of time, now almost all greeting card website is sends a link to let the person to extract the greeting card, such words collection's very inconvenient, only then has seen even. Why do web designers choose to do this, I think the idea is to increase the number of visits to the site, let us assume that if every cardholder we are asked him to be our members to read the greeting card, this is not more traffic, the result will be? My personal idea, a website should stand in the visitor's angle to look at the problem, can keep the visitor.
7. If you send a greeting card to the recipient in HTML format, the records in the library can be deleted. But keep in mind that if the recipient is using the Web to receive the letter and not be able to browse the greeting card correctly, a feature should be provided to allow the receiver to extract the greeting card by entering a key so that we may not be able to delete the record, but should save it to a time limit.
8, if the recipient of a key method, this key can be a simple and reversible ID code to generate a key.
9, delete cards should be marked first, after a period of time to delete, to ensure the integrity of the link.
10, remember that simple is beautiful, in the limited steps to complete all the operations, so that each step to complete a specific operation, and then use a red line to connect them together, less use of judgment, less with the assumption.
Finally, I wish you all success
Things are always better than you think.
Tintin
