MS Access is a highly flexible, robust, and reliable database program. Microsoft Access is the leading relational database management system in the world. We are a Microsoft Access developer company creating database applications for your business.
SQL Server is an enterprise relational database management system from Microsoft. We use SQL Server as the database server for data storage and data retrieval to and from Microsoft Access as well as other software applications, like ASP.NET and Azure.
Microsoft's application framework for web development produces dynamic web pages. ASP.NET provides web programmers with a platform for building dynamic web sites, web applications (web apps), and web services that require a web solution.
MS Azure is Microsoft's cloud computing service. It is used for development, testing and deployment as well as managing software applications through a global network data centers managed by Microsoft. Azure now features SQL Server called Azure SQL.
We Are Your Microsoft Access Database Experts
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.
Your data is important to your business and you need both to enter and retrieve data rapidly. The data stored in your company's database must be clean, secure, and allow for maximum usage. Our Microsoft Access developer team will create your Microsoft Access database for optimum efficiency with all the features you need. After we program your MS Access and SQL Server database you will have the capacity to manipulate your data so you get the information you need for every day activities and for making critical business decisions.
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.
Microsoft Access front-end and SQL Server back-end database
Access Forms Development
Access data entry form connecting to SQL Server back-end database
ASP.NET website with SQL Server back-end database
MS Access Report created with SQL Server database
Client Comments About Our Work
Sheldon Bloch, Oil and Gas Company
Alison from MS Access Solutions has provided both training and mentoring services to us over the past several years. Our developers use Alison Balter's books on programming with Microsoft Access as a desk reference. They have provided our staff members with much-needed training in Visual Basic, client/server development, SQL Server, and Microsoft Access. This has helped us to ensure that our employees can properly keep up with the ever-changing technologies. MS Access Solutions has also provided our staff with mentoring on an as-needed basis, providing expertise that helped our in-house programmers to overcome various hurdles. More Reviews
Lisa Dosch, Motion Picture Editors Guild - Local 700
Alison Balter at MS Access Solutions developed the application that helps us to properly service all of our members. This program handles billing, payments, tracking of jobs worked, available list, and other important data about our members. The system automates many tasks that were previously performed manually, allowing our employees to more cost-effectively use their time. This client/server system is used by employees in our Chicago IL and New York offices. MS Access Solutions and their staff worked with us to develop the necessary specifications and design documents, and then programmed, tested, and implemented the application throughout our organization. More Reviews
When you need a truly expert Microsoft Access database development company to design and develop your mission critical custom database - Contact MS Access Solutions.
Call MS Access Solutions at (323) 285-0939 For Complimentary Consultation
Normalization Made Easy
Normalization is a fancy term for the process of testing your table design against a series of rules that ensure that your application will operate as efficiently as possible. These rules are based on set theory and were originally proposed by Dr. E. F. Codd. Although you could spend years studying normalization, its main objective is an application that runs efficiently with as little data manipulation and coding as possible. Chapter 3 covers normalization and database design in detail. For now, here are six of the basic normalization rules:
Fields should be atomic—that is, each piece of data should be broken down as much as possible. For example, instead of creating a field called Name, you would create two fields: one for the first name and the other for the last name. This method makes the data much easier to work with. If you need to sort or search by first name separately from the last name, for example, you can do so without extra effort.
Each record should contain a unique identifier so that you have a way of safely identifying the record. For example, if you’re changing customer information, you can make sure you’re changing the information associated with the correct customer. We refer to this unique identifier as a primary key.
The primary key is a field or fields that uniquely identify the record. Sometimes you can assign a natural primary key. For example, the Social Security number in an employee table should serve to uniquely identify that employee to the system. At other times, you might need to create a primary key. Because two customers could have the same name, for example, the customer name might not uniquely identify the customer to the system. You might need to create a field that would contain a unique identifier for the customer, such as a customer ID.
A primary key should be short, stable, and simple. Short means it should be small (not a 50-character field). A Long Integer is perfect as a primary key. Stable means the primary key should be a field whose value rarely, if ever, changes. For example, although a customer ID would rarely change, a company name is much more likely to change. Simple means it should be easy for a user to work with.
Every field in a table should supply additional information about the record that the primary key serves to identify. For example, every field in the customer table describes the customer with a particular customer ID.
Information in the table shouldn’t appear in more than one place. For example, a particular particular customer name shouldn’t appear in more than one record.
Take a look at an example. The datasheet shown in is an example of a table that hasn’t been normalized. Notice that the CustInfo field is repeated for each order, so if the customer address changes, it has to be changed in every order assigned to that customer. In other words, the CustInfo field is not atomic. If you want to sort by city, you’re out of luck, because the city is in the middle of the CustInfo field. If the name of an inventory item changes, you need to make the change in every record where that inventory item was ordered. Probably the worst problem in this example involves items ordered. With this design, you must create four fields for each item the customer orders: name, supplier, quantity, and price. This design would make it extremely difficult to build sales reports and other reports your users need to effectively run the business.
shows the same data normalized. Notice that I’ve broken it out into several different tables: tblCustomers, tblOrders, tblOrderDetails, and tblSuppliers. The tblCustomers table contains data that relates only to a specific customer.
I have uniquely identified each record by a contrived CustID field, which I use to relate the orders table, tblOrders, to tblCustomers. The tblOrders table contains only information that applies to the entire order, rather than to a particular item that the customer ordered. This table contains the CustID of the customer who placed the order and the date of the order, and I’ve related it to the tblOrderDetails table based on the OrderID. The tblOrderDetails table holds information about each item ordered for a particular OrderID.
There’s no limit to the potential number of items that the user can place on an order. The user can add as many items to the order as needed, simply by adding more records to the tblOrderDetails table. Finally, I placed the supplier information in a separate table, tblSuppliers, so that if any of the supplier information changes, the user has to change it in only one place.
This material orginally 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 Chicago IL business, phone 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 companies, 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.