Code SOP-1

1. Compilation parameters cannot be confused with command line parameters.
2. Set the connection cursor before open.
3. Use set and get in the naming of functions and methods.
4. The statement in the function is indented into a tab.
5. All projects must start from the main function.
6. Multiple Functions maintain one empty row.
7. ProgramDiscard is deleted first during reconstruction.Code.
8. Remove useless references before program refactoring.
9. File Name: FRM (form), m (module), C (class ).
10. Defense programming is recommended.
11. We recommend that you use compact functions of small blocks.
12. The global variable must be prefixed with G.
13. The function name must reflect the meaning of the function.
14. Avoid typos in comments during revision.
15. Note synchronization must be ensured during function revision.
16. Dal is the abstraction layer for data access.
17. DBL is the business logic layer of data.
18. Mtools is a common tool and function for businesses.
19. Use Function naming rules that are consistent with SQL statements, such as getstudentinfobyid.
20. Module-level variables can use M or the type of the variable as the prefix.
21. Comments at the module level are placed after option explicit.
22. When using project files in VSS, do not use them.
23. During the reconstruction process, only small-scale changes are allowed to avoid modifying the program logic, but errors should be promptly revised.
24. The names of variables and functions should be written as far as possible rather than words.
25. When calling functions in other modules, add the module name whenever possible.
26. When restructuring, you must start with calling the Function Actively and gradually modify the passive service function.
27. SQL statement keywords must be capitalized.
28. In SQL query, note the interference query with spaces at the end.
29. In database operations, note that the returned value is null.