Access 2013: The Missing Manual

Errata for Access 2013: The Missing Manual

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date Submitted
Printed Page 242
1/3 down the page

The Order of Operations known as PEMDAS specifies that Multiplication is performed before Division.

The book says it backwards as Division and Multiplication and it never really explains the proper order.

Anonymous  Mar 16, 2021 
Printed Page 838
All pages in Appendix A

The pages numbers given in the index are not the same as the page numbers where the info actually is - they are consistently out of sync with each other by four or five pages.

Appendix A - Personalizing the Ribbon
Saving/reusing customized: Index 838, Actual 833
(page 838 is Index 'Cs and Ds')

Anonymous  Mar 12, 2016 
Printed Page 842
All pages in Ch 23, Import & Export Operations

The pages numbers given in the index are not the same as the page numbers where the info actually is - they are consistently out of sync with each other by four or five pages.

Eg: Index entries about importing data . . .
overview: Index 794, Actual 789
danger of duplicate records: Index 804, Actual 800
from Excel files: Index 804-807, Actual 800-803
reusing settings: Index 811-813, Actual 807-809
importing from XML file: Index 823-824, Actual 819-820

Page 823 is in fact the first page of Appendix A

All the pages affected seem to only be in chapter 23, the 'Import and Export Operations' section (that's where I've noticed it) but may affect other parts of the index/book.

Anonymous  Mar 12, 2016 
Printed Page 270
2nd paragraph

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.

Greg Fox  Feb 20, 2016 
Printed Page 850
Index entry - TCP/IP protocol

Current - TCP/IP protocol, 743
Should be - TCP/IP protocol, 741

Dennis Clinefelter  Aug 04, 2015 
Printed Page 593
Last paragraph

Visual Basic edit printed. Surely should be Visual Basic Editor?

Rod Manson  May 07, 2015 
PDF Page 547
5th Paragraph

3. Add the actions you need.
[WantsEmail]=Yes And IsNull([EmailAddress].
In the above line there was a typo and a closing bracke was omited at the end.

It should have been like so:

[WantsEmail]=Yes And IsNull([EmailAddress]).

I would say the book solidifies my understanding on Access. I use it as my reference so far i like what i read. Keep the good work up.

Mohamed Rashid

Mohamed Rashid  Mar 26, 2015 
Printed Page 418
Para 5.

In numbered para 5., there is an extra lower-case "w" in the word "Wizard".
It reads: "Wwizard" but should read: "Wizard"

Terry Janzer  Feb 16, 2015 
Printed Page 103
Figure 3-6

"Top: In this example, the First-Name and LastName field are frozen."
And the word "field" should be "fields".

Michael G  Jan 24, 2015 
Printed Page 103
Figure 3-6

"Top: In this example, the First-Name and LastName field are frozen."
The field is "FirstName", as shown in the Bottom description and in the illustrations.

Michael G  Jan 24, 2015 
Printed Page 104
Figure 3-7

As reported by Al Rhodes below, "2 or 7" should be "2 of 7".

Michael G  Jan 24, 2015 
Printed Page 117
2nd and 3rd bullet points on the page

Refers to datasheet as spreadsheet.

Michael G  Jan 24, 2015 
Printed Page 132
Figure 4-3

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

Michael G  Jan 24, 2015 
Printed Page 24

2 font sizes used in answer.

Michael G  Jan 24, 2015 
Printed Page 17
last line

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

Anonymous  Jan 10, 2015 
Printed Page 177
Tip box

Double period after "datasheet" in the Tip box.

Sergei Karacharov  Nov 26, 2014 
Printed Page 160
Full page

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

Sergei Karacharov  Nov 25, 2014 
PDF Page 369
3rd paragraph

In the paragraph (on the KEEP TOGETHER property):

If set to Yes, Access never splits the Detail section
over a page break in a printout. If there isn’t
enough room for a complete record left on a
page, Access skips straight to the next page and
resumes printing the next YEAR.

The word YEAR makes no sense.

Carlos Oliveira  Nov 06, 2014 
Printed Page 550-554
United States

The text describes a Products_Audit table and all the macros that accompany that table.



Jack Ulsh  Jun 25, 2014 
Printed Page 372-380
Sample Reports for Chapter 11

All of your sample reports for Chapter 11 have a similar error. They all set the report width to 8 inches. When this is combined with the page margins it always causes a blank page to be printed between every report page. I changed the report width to 7.5 inches on the property sheets and the problems were resolved.


Jack Ulsh  Jun 22, 2014 
Printed Page 103

Come on Man.............

This is going to be my last error report, I'm getting a little disenchanted.

Your sample data for chapter 3 has three different databases (Bobblehead, DatingService, and PastaShop). None of those have a table named Contacts that is shown in your example Figure 3-6 on page 103.

Is this really that difficult? The download that claims to be for all chapters of the book is actually a download for every MS product as far as I can tell.

The book does not make a clear reference from the examples to the sample data, the reader is left to hunt through the sample data to attempt to find the appropriate example. AND IN THIS PARTICULAR INSTANCE COMES UP EMPTY.

The text of the book is very good. It's a shame that the sample data trashes it.

This is my third submission, I wonder if anyone is reading them???

Jack Ulsh  Jun 16, 2014 
Printed Page 847
Index entry to Run Time Mode

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


Jack Ulsh  Jun 16, 2014 
Printed Page 60
Figure 2-4

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".

Jack Ulsh  Jun 16, 2014 

The tab names in 2013 are in capital letters.

Mihai Zamfirescu  Feb 12, 2014 
Printed Page 244
First sentence in the "Query Functions" section

The sentence reads, "By now, it may have2 crossed your mind..."
Obviously, you didn't mean to put a 2 in have.

Anonymous  Jul 25, 2013 
Other Digital Version 2175
Figure 3-7

Kindle version

Figure 3-7:

...(where it says "2 or 7" in this example)...

should read,

...(where it says "2 of 7" in this example)...

Al Rhodes  Jul 16, 2013 
Printed Page 655
2nd bullet point at top of page

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.

Bob Larson  Jul 13, 2013 
Printed Page 578
UP TO SPEED callout

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.

Bob Larson  Jul 13, 2013 
Printed Page 576
Gem in the rough callout

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.

Bob Larson  Jul 13, 2013 
Printed Page 222
3rd paragraph

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.

Bob Larson  Jul 13, 2013 
Printed Page 106
United States

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.

Bob Larson  Jul 13, 2013 
Printed Page 104
Figure 3.-7

The diagram shows the "record number" in the navigation. It says, "jump to a specific record." This should probably be clarified especially for new users who might not know. This number is only relative to the currently loaded recordset. It should not be relied upon to actually go to a specific record in most cases. Since tables are not stored in any particular order, unless the records do not get added/deleted from the table and a query with a sort order is used for the form's record source, the number 7 record can, and is likely, to not refer to the same record over time. This is a common mistake made by new users.

Bob Larson  Jul 13, 2013 
Printed Page 426
12th line of char on that page

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.

Nan Barber  Jun 25, 2013 
Printed Page 566
3rd paragraph of sidebar

The URL should be

Nan Barber  Apr 11, 2013