Part 5 - Various tips
Document, document, document
For all shortcuts, naming specifications, restrictions, and functions must be programmed.
- NickypendRagon
Use database tools that are added to tables, columns, triggers. Yes, this is a little time, but from the long run, do it to open
It is very useful for sending, supporting and tracking modifications.
- Chardove
Depending on the database system you use, some software may give you some documentation for you to get started. You may want to open first
Starting, then get more and more details. Or you may want a periodic prevention, in the input of new data, along with you
Advances to each part of detail. No matter which way you choose, you must always make your database documentation, or in your database itself.
Interior or separate documentation. In this way, when you have been going over more than a year, I will return to the 2nd version, you make mistakes.
It will be greatly reduced.
- MRS_HELM
2. Use common English (or any other language) instead of using coding
Why do we often use coding (such as 9935A may be the supply code of the ink pen, 4xF788-q may be an account editor
code)? Reason a lot. But users usually think in English rather than coding. Accounting for 5 years, perhaps
What is 4xF788-q, but the new can be not necessarily. By creating a drop-down menu, a list, it is best to follow English.
Name sort. If you need to be encoded, then you can attach the user knows English.
- AMASA
3. Save common information
It is useful to make a table to store general database information. I often store the current version of the database in this table, recently check / repair
Reclusion (for Access), the name of the design document, customers, etc. This can achieve a simple mechanism tracking data
Library, when customers complain that their database does not meet your desire to contact you, doing this to non-client / server environment
Particular useful.
- Richard Foster
4. Test, test, repeated test
After establishing or revising the database, you must use the data field to test the data field with the user. Most importantly, let users test
Try and to ensure that the data type you choose meets business requirements. Test needs to put new databases into actual services
Pre-completion.
--Juneebug
5. Check design
The common technologies for checking database designs during development are through their supported application prototypes. in other words,
For each of the final expression of data, you must ensure that you check the data model and see how to remove data.
- JGootee
6. Access design skills
For complex Microsoft Access database applications, you can put all the primary tables in a database file,
Add other database files and load special functions related to the original database. Connect these functions to the main file as needed
The primary table in. For example, data input, data QC, statistical analysis, provide reports to management or government departments and various types of read only
Query, etc. This step simplifies the allocation of users and group permissions, and is conducive to the packets and divisions of the application function, thus
It is easy to manage when the program must be modified.
- Dennis Walden
