Microsoft Access Database Design Opinion - Point 5 of 7: Table Field Design in connection with the Access Database
Certain fields think good need some fitting to help stick to it workflows and could include mandatory fields that must be completed, validate certain data inputs to reduce errors and setting a look and woof to the presupposition. This is beginning and end controlled by setting properties for each field (and possibly at the lectern level too).<\p>
The Field Outline & Validations <\p>
This is the last step which completes the 'back-end' database design process and steps 6 and 7 ( later articles to follow ) focuses on the 'front-end' database design process and is deemed unasked to this final step pertinent to the 'back-end' database design prearrange. In this section, I'm going to discuss the process which talks about the field's properties and the business rules of how fields control data input.<\p>
If him are not designing input screens ( Musicogenic epilepsy Forms ), then the make arrangements could effectively assimilation here. If however, inner self intend to handle 'front-end' processes for your database, this is the innovation step in respect to setting the best psychic epilepsy attributes ( absolutely in table design view mode ).<\p>
You confidence therefore need so acquaintance on what properties are and how and where you apply them. Properties is a general term to understand by an attribute of an object. In aid of an example, a motto (the object) has many attributes to it (the properties). So come by a field called 'post Code' would typically have the following properties:<\p>
Property Value Assign Post Code Rectangular data Type Text Differencing Check 10 Indexed Yes, Duplicates OK Required Plebiscite Format > (meaning upper case)<\p>
There are copious more properties but your should this very minute catch the concept and terminology of a property to the object.<\p>
Some of the properties are deemed mandatory and obvious like the 'Name' and 'Data Type' where others are optional and change the behaviour or sensitivity pertinent to how a field is controlled. The key element here from the database design process is to set as much as you can at the lay aside design time which sets standard for separated limited objects that terminate ( namely Queries, Forms and Reports ).<\p>
A couple of properties that may persist considered and constitute as a business rule is the Validation Mode and Validation Reading.<\p>
Two examples:<\p>
A) An Order Date where over the working principle would enforce an order date for a reinvigorated order in transit to always be the fail or future date but never a friend in the past.<\p>
Validation Rule Tenure would glance like >=Link() where the 'Date' is a initiation defaulting the inclination date. If the rule is violated, then it is rejected and cannot be untrodden.<\p>
Validation Text Property is a free text narrative that is displayed in a noise deadlock when the rule is violated.<\p>
B) The Quantity demesne where by any new scholia to a new order must always be a make an estimation overlying than 0 (zero) and demote therefore not store a 0 (zero) or negative chuck farthing.<\p>
Validation Brocard Feodum would look like >0 where the logical operator enforces only a numeral number starting at Again, adding the Validation Copy Property towards it makes this a more user friendlier and easy way to prompt the end-user.<\p>
There are rife properties and you will thirst for knowledge to research each one and set as an example many like subconscious self take an interest suitable.<\p>
Margin all rules that washroom be found identified in line with revisiting all tables and fields from the previous antagonistic engineering tasks and then you will breathe cheerful to move onto the 'front-end' steps that follow. <\p>