Access Design View Conclusion
This module discussed Access Design view and working with both forms and reports. You should be getting more comfortable working with them by now you should also be convinced that Design view is a bit of a pain,
and it is worth your while to start a report (or a form for that matter) with a wizard.
Although you have learned a lot about reports here, there is plenty more to learn. If you find yourself frustrated when you can not make a report look exactly as you want it to, it might be because you have not learned the right skill yet.
Make liberal use of Access's Help system since there is a lot of information there.
When you use the Query Design View in Access, you are actually building a SQL statement. Most of the time, you will not actually need to look at the SQL code, but you can see it using the SQL view if you are curious.
Conversely, you can take most SQL statements, paste them into the SQL view of a new query, and then switch over to Design view to see how they work. There are a few types of SQL statements
for which this will not work. For example, union queries and pass-through queries cannot be viewed using Design view.
Even if you’re comfortable using SQL in queries, you may not be familiar with building SQL statements in VBA. If you are not, you are missing out this functionality.
Using SQL in VBA is a powerful technique that can enable many great features in your Access applications. By using VBA, you can build custom SQL statements for combo boxes, forms, and reports.
For example, you will be able to change the sorting and selecting of records on continuous forms, control the record selection on reports, and limit the drop-down lists of combo boxes based on other combo boxes.
Terms and concepts
This module introduced you to the following terms and concepts:
- Summary calculations
In the next module you will learn about using Access 2013 tools: creating static Web pages from Access objects to present on the Web, exporting data to use in other applications, and more!