How to learn Access database programming

It seems to say in Wuxia novels: "Have you forgotten your moves?" "," said the reply, "Almost forgot," "Just forget it."

How does this relate to database programming? It's a big relationship. Did the comrades learn Pascal, BASIC, C (c + +)? If not, FOXBASE, FoxPro should have learned it? Programmed in these languages, are procedural, white point is a data, a record of a record to deal with (FOXBASE, FoxPro not exactly, but the book is often so introduced), I contacted Access 97 o'clock, suddenly without the IF, for these statements ( refers to data processing), all with SQL statements, really can't find North, fortunately I learn SQL language, also try to forget this if, for, I forget almost when Kungfu also entered a big step, the original to a large section of the program, now one or two SQL statement, even with a few more SQL statements, Because it is done in the graphical interface, visualization operations, Lalacheche, and then modify the generated SQL statements, it will be more convenient.

Since access has a complete SQL language (foxbase not, FoxPro incomplete), I started programming with access from Access 97, and so far DAO, ADO is rarely used, plus some of the techniques that have recently come in contact with Essise, essentially without DAO, ADO is OK, I can see from my "Unfinished inventory management", only occasionally in special cases. (Less, but not no, you have to learn, do not misunderstand)

How to learn database programming well? Here are some of my experience, for reference only:

1. First of all, the original data of a data, a record of a record of data processing way to forget, the more thorough the better.

Now it's in batch processing. Use less recordset to record a record and use SQL statements as much as possible.

2. Learn the relational database theory, especially the standardization theory, the table design must be standardized, at least to standardize to the third normal form. Set operation (and, intersection, difference). Relational operations (selection, projection, connection). In which the connection and normalization are closely combined.

3. The use of object-oriented technology: object-oriented analysis Ooa, object-oriented design Ood, object-oriented programming oop, based on the relationship between tables, using forms and subforms, reports and subreports, simulation of object-oriented, which can increase the readability and maintainability of the program. (This is advanced technology, comrades do not despise, big projects you will know useful)

4. When using a query, usually a step can not be done, a few steps to do, I usually do so, from the example of my reply to netizens can also be seen. Why did you do that? (1) Some are the limitations of the SQL language, no way to make a step, forced; (2) You can check the results of each step query, easy to debug, (3) Increase readability, easy to maintain later.

5. The results of the query are displayed in a form or printed in a report, and the techniques are similar. You can often change the conditions in which you open a form or report to control the range of records that are displayed or printed. When you use a query to do a data source, dynamically changing the SQL statements in a query is easier than referencing a form's control in a query, because SQL statement generation is in VBA and can be stored in character variables before the query's SQL statement is updated, so that you can use breakpoints to check the value of the variable. Debugging is difficult when you refer to a control for a form in a query, especially if the IIF () function is included.

6. Develop a system, first of all to solve the technical problem, that is, the algorithm, with a simple example, the algorithm to understand, and then detailed design, this point from the user's questions can be seen, there are many people's problem expression is not clear, some people have a lot of the algorithm has nothing to do, especially professional things, others are not easy to see, Because the algorithm is not clear, the program can not be compiled.

7. Do not use too many tool features, using too many tool features can make readability less maintainable, difficult to get help when needed, and, worse, portability, from MDB to ADP, so it's important to be readable in programming, and more important for portability, Are you willing to run your own program in one environment? Are you willing to develop with a tool forever? For your "Money path", do not play with too many skills, of course, technical research is another thing.