Errata

Under the OrderTotal bullet point, it says "so set the Total box to Sum." This is incorrect as setting to Sum will trigger a "Cannot have aggregate function in expression" error. The Total box must be set to Expression in order for the query to execute properly.

Refers to datasheet as spreadsheet.

"You can keep your changes (even though they conflict with at least one record. ..."
Closing parenthesis is missing.

reference should be to page 12, not 11 for fig. I-6

As of Access 2013 version 15.0.4667.1002, "Limit to List" function is included in Lookup Wizard.

The index points "runtime engine, Access" to page 658. There is no reference to that term on that page. The appropriate reference should be to page 656 or 657.

I know,,,,,,,,,,,,it's a nit

sorry.

Last sentence of the figure description says "Descriptions also appear in the status bar when you're entering information in a table." This appears to be a hold over from a prior version of the book.
The Note immediately following Figure 2-4 contradicts this statements and states that this is was discontinued in Access 2013 because it was found to be "relatively useless".

The statement reads, "They can't edit or even look at your VBA code and macros."

Unless they actually made that change in Access 2013 from 2010, that is incorrect. If you create an ACCDE file, they cannot edit forms, reports, or VBA. But ;they CAN still edit MACROS, tables, and queries.

The statement currently reads, "So, if you have a button that's 1.125 twips wide, and it's still too narrow, try a Width of 1.5..."

That is a bad example because a button that is even 1.5 Twips will not even show up on the form. You need to MULTIPLY that by 1440 to get a decent button width. So, if you want a button that is a quarter of an inch wide, you would use .25 * 1440 to get that to display. And yes, while inches are not really valid on a monitor screen, you must use that relative measurement multiplied by the 1440 or just know that you need 360.

The statement reads, "Technically, Me is a programming object that represents the current form."

That is not an accurate statement. Me is a programming object that represents the current CLASS object, whether it be a form, report, or other Class object.

The statement "That means you need to retrieve similar columns from each table, in the same order..." is incorrect when it comes to Access. For Access the ONLY thing that is necessary is to have the same NUMBER of columns returned from each Select statement. The data type does NOT have to be the same (unless they actually did change this for Access 2013). If you use disparate data types then Access coerces that column to Text.

The statement "Similarly, any new records that you add stay at the end of the table until the next sort (or the next time the table is opened)..." is misleading and should be clarified.

Tables in Access do not store data in any particular order. If you do a compact and repair, it attempts to rearrange by Primary Key but it does not remain ordered. And when you open a table you are actually not opening the table at all. You are, in reality, opening a system QUERY of the data stored in the table. So, when you want data in a particular order you need to apply the sort, not only in the table but also in the query, form (if not using a query with a sort) and report. The sort applied to the table view does not propagate to queries, forms, and reports.

What it says now:

If you want to provide a graphical view of your data, you?re better off using a pivot chart (see Chapter 9) or just exporting your raw data to Excel, which is much more capable.

What it should say:

If you want to provide a graphical view of your data, you?re better off exporting your raw data to Excel, which is much better suited to creating sophisticated charts.

The URL http://tinyurl.com/access-VBA should be http://tinyurl.com/accessVBA