The first principle is that duplicate information (also called redundant data) is bad, because it wastes space and increases the likelihood of errors and inconsistencies.

Top of Page What is good database design?Д¬ertain principles guide the database design process. Each column or field holds some type of information about that product, such as its name or price. In the Products table, for instance, each row or record would hold information about one product. A field is a single item of informationВ - an item type that appears in every record. A record is a meaningful and consistent way to combine information about something. For example, you might have a table that stores information about products, another table that stores information about orders, and another table with information about customers.Д®ach row is more correctly called a record, and each column, a field. For most databases you will need more than one. In a simple database, you might have only one table. In this articleДЇinding and organizing the required informationДЄccess organizes your information into tables: lists of rows and columns reminiscent of an accountantвЂ™s pad or a spreadsheet. For more information, see the article Build a database to share on the Web. This article doesn't discuss Web database application design. Many design considerations are different when you design for the Web. Access provides design experiences that let you create database applications for the Web.

The best database software construction