Handling Many To Many Relationships
Definition: Many-to-many (M:M) - is used to relate many records in the table A with many records in the table B. A record ('parent') in Table A can have many matching records ('children') in Table B, and a record ('child') in Table B can have many matching records ('parents') in Table A.

Introducing Higher Normal Forms
Designing your tables to comply with 3NF (third normal form) is usually sufficient to ensure good design so, most of the time, you can stop right here. The higher normal forms address less common data problems. They are included here so you'll know what they are and what to do about them if you come across them. These normal forms do get a bit more complicated.

Preventing Duplicates from being entered
There will always be situations where you need to ensure that you do not have duplicates entered into your database. Ideally you will want to validate data at the lowest level possible, so if you can enforce the rules at the table level (using Primary Keys), that's great.

Relational Database Normalisation Process
Illogically or inconsistently stored data can cause a number of problems. In a relational database, a logical and efficient design is just as critical. A poorly designed database may provide erroneous information, may be difficult to use, or may even fail to work properly.

Sending E Mails from a Microsoft Access Database
As with many other options there are various techniques and approaches to sending e-mails via a Microsoft Access Database and here you will find one working example of how to achieve this.

Your Database First Normal Form
Database design theory includes design standards called normal forms. The process of making your data and tables match these standards is called normalizing data or data normalization. By normalizing your data, you eliminate redundant information and organize your table to make it easier to manage the data and make future changes to the table and database structure.