If your database contains incorrect information, any reports that pull information from the database will also contain incorrect information. The second principle is that the correctness and completeness of information is important. 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.
0 kommentar(er)
