
MS Access As A Dev Tool
Access continues to be a highly efficient tool for business database development.
The Best Microsoft Access Database Solutions owner, consultant, and principal programmer is Alison Balter - a recognized expert Microsoft Access consultant. Alison is the author of 15 Microsoft Access training books and videos. She is a frequent guest speaker at MS Access conferences and has developed hundreds of applications for businesses of all types.
We know your business data is important; we listen to your concerns, ask questions, and gather information from all stake holders. We discuss your needs and requirements for your database. We find out what you want, why you need various features so we can obtain as much information as possible. Once we have the information we need, we work with you to design the proper database architecture, plus the dashboards, the questions (queries), forms, and reports you need for an excellent database system.
We also create websites designed for speed to display your data accurately, using ASP.NET technology. Fast, secure, and robust, our ASP.NET web sites and web applications give you true business tool for finding and displaying information dynamically on the web.
Access continues to be a highly efficient tool for business database development.
How to create a Microsoft Access application with some unique tips and tricks.
Your Access developer near me has some great info for you about using Access efficiently.
Call MS Access Solutions at (323) 285-0939 For Complimentary Consultation
Establishing Referential Integrity As you can see, establishing a relationship is quite easy. Establishing the right kind of relationship is a little more difficult. When you attempt to establish a relationship between two tables, Access makes some decisions based on a few predefined factors: 1. Access establishes a one-to-many relationship if one of the related fields is a primary key or has a unique index. 2. Access establishes a one-to-one relationship if both the related fields are primary keys or have unique indexes. 3. Access creates an indeterminate relationship if neither of the related fields is a primary key and neither has a unique index. You cannot establish referential integrity in this case.
As covered earlier in the chapter, referential integrity consists of a series of rules that the Access Database Engine applies to ensure that it properly maintains the relationships between tables. At the most basic level, referential integrity rules prevent the creation of orphan records in the table on the many side of the one-to-many relationship. After a relationship is established between a Customers table and an Orders table, for example, all orders in the Orders table must be related to a particular customer in the Customers table. Before you can establish referential integrity between two tables, the following conditions must be met: 1. The matching field on the one side of the relationship must be a Primary Key field or must have a unique index. 2. The matching fields must have the same data types (for linking purposes, AutoNumber fields match Long Integer fields). With the exception of Text fields, they also must have the same size. Number fields on both sides of the relationship must have the same size (Long Integer, for example). 3. Both tables must be part of the same Access database. 4. Both tables must be stored in the proprietary Access file (.ACCDB) format. (They cannot be external tables from other sources.) 5. The database containing the two tables must be open. 6. Existing data within the two tables cannot violate referential integrity rules. All orders in the Orders table must relate to existing customers in the Customers table, for example.
After you establish referential integrity between two tables, the Access Database Engine applies the following rules: 1. You cannot enter a value in the foreign key of the related table that does not exist in the primary key of the primary table. For example, you cannot enter a value in the CustomerID field of the Orders table that does not exist in the CustomerID field of the Customers table. 2. You cannot delete a record from the primary table if corresponding records exist in the related table. For example, you cannot delete a customer from the Customers table if related records exist in the Orders table (records with the same value in the CustomerID field). 3. You cannot change the value of a primary key on the one side of a relationship if corresponding records exist in the related table. For example, you cannot change the value in the CustomerID field of the Customers table if corresponding orders exist in the Orders table.
If you attempt to violate any of the preceding three rules and you have enforced referential integrity between the tables, Access displays an appropriate error message.
This material originally appeared in Alison Balter's book Mastering Microsoft Office Access 2007 Development. Reprinted here by author's permission.
When you need a Microsoft Access programmer for your Tuscon AZ business, call MS Access Solutions at (323) 285-0939. We have over 25 years experience in Microsoft Access programmer solutions. We create Access database applications for all sectors, consisting of hospitals, government agencies, the U.S. military, universities, agriculture, workers services, and insurance provider. We can take care of the most advanced as well as complicated Access and also SQL Server database programming for your business as well as smaller projects, like fixing damaged Access database forms, MS Access reports, Access macros, and VBA code.
More Access programmer cities we serve: Access Programmer Austin TX