When and When Not to Bind a Form to a Query

In this Microsoft Access tutorial, I'm going to show you when you should and should not build a form based on a query. We'll see when it's useful, when it's harmful, and when you absolutely should not do it.

Kieran from Newton, Massachusetts (a Platinum Member) asks: I'm relatively new to Microsoft Access, but with the help of your tutorials, I'm making a lot of progress. Thank you. One problem that I'm having is that I tried to make a continuous form where I can see customers and their order information, but whenever I try to edit something like the customer's address, it ends up changing all of the orders. I have my form based on a query that joins customers, orders, and order details, but I'm not doing something right. Can you shed some light on this?

Prerequisites

• Relationships

Links

• Invoicing
• Calculated Fields
• Not Updateable
• Form Footer Totals
• Subforms

Recommended Courses

• Access Expert Courses

Learn More FREE Access Beginner Level 1 FREE Access Quick Start in 30 Minutes Access Level 2 for just $1 Free Templates TechHelp Free Templates Blank Template Contact Management Order Entry & Invoicing More Access Templates

Resources Mailing List - Get emails when new videos released Consulting - Need help with your database Tip Jar - Your tips are graciously accepted Questions? Please feel free to post your questions or comments below or post them in the Forums.

Keywords

TechHelp Access, Continuous form, multiple table query, form based on query, non-updatable record sets, subforms, one-to-many relationships, form footer totals, calculated fields in queries, action queries, VB for Access, Access form design best practices