Access 2007: The Missing Manual

Errata for Access 2007: 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. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Printed
Page 000
missing CD web page

the URL link for "VBA (Visual Basic for Applications) reference" is broken

Anonymous   
Printed
Page 9
figure 1-4, in figure and text 2nd half

W should be Q: (for example, W moves your data to SQL Server) should be: (for example, Q moves your data to SQL Server)

Heer Henk  Jan 11, 2009 
Printed
Page 16
Figure 1 - 10

Reads; When you're designing a form..... Should be: When you're designing a table...

Note from the Author or Editor:
"When you're designing a form" should be "When you're designing a table"

Anonymous  Feb 26, 2009  Apr 01, 2009
Printed
Page 42
4th line from bottom

even attempt do anything vs. even attempt to do anything

Anonymous    Apr 01, 2009
Printed
Page 59

Under the "word to the wise" section, the last sentence "if you suspect trouble, switch to Design View,..." should be "switch to Datasheet View"

Anonymous    Apr 01, 2009
Printed
Page 67
Bottom of the page, first bullet

The date is listed as year-day-month (2008-23-2) but it is called "the international year-month-day standard"

Note from the Author or Editor:
2008-23-2 should be 2008-2-23 in first bullet point on page 67; may already be corrected in current printings.

Anonymous   
Printed
Page 77
Next-to-last paragraph

Says "Every table must have a primary key." Access doesn't require that a table have a primary key, so "must" is a bit strong. Certainly every Access table should have a primary key by the time a database designer is done, but the lack of a primary key requirement is helpful at times early in the design process.

Note from the Author or Editor:
change "must have" to "should have", although this change may have been made already

Anonymous   
Printed
Page 79
Note in middle of page

The described procedure (using "drag the mouse to select more than one field") implies that only adjacent fields can be joined to create a composite primary key. Using the Ctrl key to multi-select fields (and keeping it pressed while right-clicking), you can also select non-adjacent fields.

Note from the Author or Editor:
replace "First, click the margin next to the field name, and then drag the mouse to select more than one field. Then, hold down Shift, and then right-click your selection." with "Hold down the Ctrl key, and click each field you want to include, one after the other. Then, while holding down Ctrl, right-click your selection."

Anonymous   
Printed
Page 79
Second paragraph, last sentence

should be "is more work tha[n] is seems"

Anonymous    Apr 01, 2009
Printed
Page 82

"All you'll see in this book, you can easily filter out the information you don't need from the datasheet..." should read "As you'll see in this book,..."

Anonymous    Apr 01, 2009
Printed
Page 89
2nd paragraph under heading - Rearranging Columns, 3rd sentence

Sentence begins "From right to left". It should be "From left to right".

John Pursell  Jun 09, 2009  Sep 01, 2009
Printed
Page 93
3rd paragraph

The sentence states "Frozen columns must always be positioned at the left size of the datasheet." It seems like it should say "Frozen columns must always be positioned at the left SIDE of the datasheet."

Anonymous    Apr 01, 2009
Printed
Page 96
1st paragraph

Says "In an unsorted table, records are ordered according to when they were created, so that the oldest records are at the top of the datasheet..." Records in Access are ordered according to the primary key. When a non-random ID field is used as the primary key (as the author recommends elsewhere in the book), the records do appear to return in chronologically-entered order because the chosen primary key increases in chronologically-entered order. However, in other cases - and they are very common - the pattern described in the book is inaccurate. (Note: I'm aware that a true database expert would say that the order of records in a database should be considered indeterminate, but that's a bit picky.)

Note from the Author or Editor:
remove sentence "In an unsorted table, records are ordered according to when they were created, so that the oldest records are at the top of the datasheet, and the newest at the bottom. "

Anonymous   
Printed
Page 96
end of "Up to Speed"

I tried the sorting mentioned in the "Up to Speed" and #'s always sorted before letters in my attempts. If I am correct, the list should read: 1. blank (empty) values 2. space 3. special characters 4. numbers 5. letters

Note from the Author or Editor:
The correct list has the last two items reversed. It should be: 1. Blank (empty) values 2. Space 3. Special characters (like punctuation) 4. Numbers 5. Letters Type of error

Anonymous  Nov 28, 2008  Apr 01, 2009
Printed
Page 98
1st sentence

Missing word (likely "a"): "In order to filter records, you specify a condition that [missing word here] record must meet ..."

Anonymous    Apr 01, 2009
Printed
Page 102
penultimate line

Should be: 1. Choose Home --> Find --> Find (not Choose Home --> Sort & Filter --> Find) [at least that's how it is on my system)

Anonymous  Jun 02, 2008  Dec 01, 2008
Printed
Page 102
Step 1 at bottom of page

Says "Choose Home --> Sort and Filter --> Find". Should be "Choose Home --> Find --> Find."

Anonymous    Apr 01, 2009
Printed
Page 109
figure 3-18

In the Replace box, "PEDS" should be "PESDS," to agree with the caption.

Anonymous  Jun 02, 2008  Apr 01, 2009
Printed
Page 109
figure 3-18

In the Replace box, "PEDS" should be "PESDS," to agree with the caption.

Anonymous    Apr 01, 2009
Printed
Page 121
First sentence, continuing from p. 120

Says "a field," should say "an index.": "... which means Access doesn't create [an index]."

Anonymous    Apr 01, 2009
Printed
Page 123
figure 3-18

Paragraph beginning "You can also...": Insert the word "set" as follows: "In this case, you should set Ignore Nulls to Yes."

Anonymous  Jun 02, 2008  Dec 01, 2008
Printed
Page 123
top of page

Paragraph beginning "You can also...": Insert the word "set" as follows: "In this case, you should set Ignore Nulls to Yes."

Anonymous    Apr 01, 2009
Printed
Page 127
figure 4-12

Change "chosen" to "stored" as follows (?): The final step lets you choose how the data in your field is stored--with or without the mask symbols.

Anonymous  Jun 02, 2008  Dec 01, 2008
Printed
Page 127
figure 4-12

Change "chosen" to "stored" as follows (?): The final step lets you choose how the data in your field is stored--with or without the mask symbols.

Anonymous    Apr 01, 2009
Printed
Page 153
last paragraph:

p.153 last paragraph: 8. To define your relation ship ... (parent and child should be switched, you drag the field from the child table to parent table, not the other way round)

Note from the Author or Editor:
(153) step number 8, "find the field you're using in the parent table" shoud be "find the field you're using in the child table" and "to link it to in the child table" should be "to link it to in the parent table"

Anonymous  Mar 30, 2009  Apr 01, 2009
Printed
Page 164
figure 5-12

Delete the last sentence ("One links students...") from the figure legend.

Anonymous  Jun 02, 2008  Dec 01, 2008
Printed
Page 164
figure 5-12

Delete the last sentence ("One links students...") from the figure legend.

Anonymous    Apr 01, 2009
Printed
Page 165
middle

Change "design" to "datasheet" (?) in: "Now, if you switch to the design view..."--> "Now, if you switch to the datasheet view..."

Anonymous  Jun 02, 2008  Dec 01, 2008
Printed
Page 165
Sentence above Figure 5-14

Says "if you switch to the design view of the Dolls table..." Should say "if you switch to the datasheet view of the Dolls table..."

Anonymous    Apr 01, 2009
Printed
Page 185
Top third of page, second bullet

The second line of the bulleted text begins "which is a piece text". Should this read "which is a piece of text..."?

Note from the Author or Editor:
p. 185 "which is a piece text" should be "which is a piece of text"

Anonymous  May 23, 2008 
Printed
Page 185
Top third of page, second bullet

The second line of the bulleted text begins "which is a piece text". This should this read "which is a piece of text..."

Anonymous    Apr 01, 2009
Printed
Page 187
figure 6-3

Add phrase before "drag the gray bar" as follows: "To reorder your columns, select the column and then drag the gray bar..."

Anonymous  Jun 02, 2008  Dec 01, 2008
Printed
Page 187
figure 6-3

Add phrase before "drag the gray bar" as follows: "To reorder your columns, select the column and then drag the gray bar..."

Anonymous    Apr 01, 2009
Printed
Page 192
Tip

page 119 should be page 229 (?)

Anonymous  Jun 02, 2008  Dec 01, 2008
Printed
Page 192
In Tip:, 3rd paragraph from bottom

The cited page number should be 229, not 119.

Anonymous    Apr 01, 2009
Printed
Page 198
In Note:, 3rd paragraph from bottom

Misspelled word(s): in the second set of parentheses, "SQL Server" is incorrectly spelled "SQL Sever." Also, just prior to that, the word "name" should probably be either "named" or it should be deleted.

Anonymous    Apr 01, 2009
Printed
Page 206
Note

Change "classes" and "instructors" to "orders" and "customers," as in: "you end up with: a list of orders or a list of customers"

Anonymous  Jun 02, 2008  Dec 01, 2008
Printed
Page 206
"Note:" section

It is printed, "... then what do you end up with: a list of classes or a list of instructors?" This should be, "...then what do you end up with: a list of orders or a list of customers?" You had mixed up the school example.

Anonymous    Apr 01, 2009
Printed
Page 230
In POWER USERS' CLINIC

The first right parenthesis in the example formula is in the wrong place - it's too far to the right, and the result appears as an error in Access. The formula should be FirstWordProduct: Left([ProductName],InStr([ProductName]," ")-1) (Minor point: The "S" should be capitalized in the middle of "InStr" too - it's incorrectly shown as "Instr" in at least nine places in the POWER USERS' CLINIC block.)

Anonymous    Apr 01, 2009
Printed
Page 231
1st paragraph in WORD TO THE WISE

Misspelled word - says "... for you date field," should be "... for your date field."

Anonymous    Apr 01, 2009
Printed
Page 233
Bottom of page

The formula should include a space: [FirstName] & " " & [LastName], ...

Anonymous    Apr 01, 2009
Printed
Page 241
point 5, first paragraph

Might specify that [CustomerState] would go in the Criteria Box

Note from the Author or Editor:
p. 241, "add the following filter condition to the State field" should be "add the following filter condition to the Criteria box for the State field"

Anonymous  Jun 02, 2008 
Printed
Page 261
2nd paragraph

"In (14,15,18)" This filter expression matches any records that have ID values 14,15, or 16. it should read "14,15,18"

Note from the Author or Editor:
p. 261, second paragraph, "values of 14, 15, or 16" should be "values of 14, 15, or 18"

George Kanakis  Sep 12, 2009 
Printed
Page 266
In the Summary Smackdown Box

In the first bullet, it states that one should use a totals query if grouping with one field. It then points to the top of Figure 9-1 as an example. Figure 9-1 in fact shows 2 levels of grouping, not one.

Note from the Author or Editor:
p. 266, first bullet point, remove "(as shown, for example, in Figure 9-1, top)"

Anonymous  Aug 16, 2009 
Printed
Page 272
Last Paragraph

The sentence: "Although the Crosstab wizard limits you to three fields for row grouping, you can actually add a virtually unlimited number of fields for COLUMN grouping." Instead of "column" this should read "row" as you must use exactly one field for column grouping.

Note from the Author or Editor:
p. 272, Change "a virtually unlimited number of fields for column grouping" to "as many as you want in Design view"

GoodyKags  Apr 01, 2009 
Printed
Page 302
note

cross-ref to page 206 should be to page 306

Anonymous  Jun 02, 2008  Dec 01, 2008
Printed
Page 310-318
throughout the pages

When indicating the ribbon commands for formatting reports, the book consistently identifies "Report Layout Tools | Format" incorrectly as "Report Layout Tools | Formatting." The correct ribbon section name is Format not Formatting.

Note from the Author or Editor:
pages 310-318, "Report Layout Tools | Format" is sometiems incorrectly referred to as "Report Layout Tools | Formatting." This is fixed in the Access 2010 edition.

Anonymous  Dec 29, 2009 
Printed
Page 355
United States Figuse 11-27

It would appear that what is titled "Order Total:" is in acuality the total of the unit prices of the items ordered, a relatively meaningless number. The total of the extended prices ($398.99) does not appear.

Note from the Author or Editor:
A better example with a calculated field is being substituted in next edition.

Anonymous  Jan 17, 2010 
Printed
Page 379
under point 2

"top-right corner" might actually be "top-left corner" (that's where it is on my system)

Anonymous  Jun 02, 2008  Dec 01, 2008
Printed
Page 379
under point 2

"top-right corner" might actually be "top-left corner" (that's where it is on my system)

Anonymous    Apr 01, 2009
Printed
Page 396
bottom of table

opposite "Page Break," change "usfe" to "use"

Anonymous  Jun 02, 2008  Dec 01, 2008
PDF
Page 396
within table under 'Bound Object Frame'

Erroneous repeat of 'with an attachment control': "using an attachment field with an attachment control (page 72), with an attachment control,"

Note from the Author or Editor:
"using an attachment field with an attachment control (page 72), with an attachment control, which is designed" should be "using an attachment field with an attachment control (page 72), which is designed"

Anonymous  Nov 06, 2008  Apr 01, 2009
Printed
Page 404
In the second step paragraph

It references Figure 13-9 here. In fact, it's supposed to be Figure 13-8.

Note from the Author or Editor:
p. 404, paragraph under step 2, reference to Figure 13-9 should be 13-10

Anonymous  Aug 03, 2009 
Printed
Page 444
Step 2

The line beneath bold line in step 2, says: "...choose the Format Operations category" "Format" should be change to just "Form"

Note from the Author or Editor:
p. 444, step 2, "choose the Format Operations" should be "choose the Form Operations"

Michael Duplantier  Aug 21, 2009 
Printed
Page 487
penultimate paragraph

In the sentence that begins "The only drawback's...": Insert "you" (or similar) between "doesn't let set"

Anonymous  Jun 03, 2008  Apr 01, 2009
Printed
Page 487
penultimate paragraph

In the sentence that begins "The only drawback's...": Insert "you" between "doesn't let set"

Anonymous    Apr 01, 2009
Printed
Page 489
paragarph that starts "_And_ enforces two conditions"

Unless I'm completely mixed up, either the last line of that paragraph should read "...the FirstName and the LastName fields are SHORTER than three characters a piece" OR the less-than signs in the next line should be greater-than signs.

Anonymous  Jun 03, 2008  Dec 01, 2008
Printed
Page 492
last paragraph, 2nd sentence

"The number 4 tells Access TO THAT the Message box..." delete "to" (or add text, if something is missing)

Anonymous  Jun 03, 2008  Apr 01, 2009
Printed
Page 492
last paragraph, 2nd sentence

"The number 4 tells Access TO THAT the Message box..." delete "to"

Anonymous    Apr 01, 2009
Printed
Page 518
After 1st paragraph

In the example that shows how to write a code in the case of 'Esc' being pressed, the following event is missing "Cancel As Integer" in the parenthesis. (Although it is included in the download-able examples.)

Note from the Author or Editor:
p. 518, first line of code: Private Sub Form_Undo() should be: Private Sub Form_Undo(Cancel As Integer)

Anonymous  Jan 05, 2010 
PDF
Page 575
'Troubleshooting moment'

"WITH the .laccdb file, Access has no way to coordinate multiple users." should read "WITHOUT..."

Note from the Author or Editor:
"with the .laccdb file, Access has no way to coordinate multiple users" should be "without the .laccdb file, Access has no way to coordinate multiple users"

Anonymous  Nov 13, 2008  Apr 01, 2009
Printed
Page 593
Note near middle of page, the paragraph above it, and the next-to-last bullet on the page

The Note says, in part, "In order to successfully use a password with a back-end database, you must apply the password before you split the database." The second paragraph of Microsoft's Database Splitter wizard window disagrees: "If your database is protected with a password, the new back-end database will be created without a password and will be accessible to all users. You will need to add a password to the back-end database after it is split." When I use the book's recommended approach, I can open the back-end database directly without a password - it isn't secure at all, just as Microsoft's warning states. The front-end remains protected with the pre- entered password. When I use Microsoft's recommendation to password-protect the back-end after a split, my wizard-created front-end database no longer can access the linked tables, even when the passwords are identical.

Note from the Author or Editor:
The correct process is in the Access 2010 edition. It is: 1. Split the database. 2. Encrypt the back end. 3. Delete the linked tables in the front-end, and add them back by re-linking the database. 4. Encrypt the front end with a different password.

Anonymous   
Printed
Page 593
last sentence before Note

"That means that as long as..." (not "as along as...")

Anonymous  Jun 08, 2008  Apr 01, 2009
Printed
Page 593
last sentence before Note

"That means that as long as..." (not "as along as...")

Anonymous    Apr 01, 2009
Printed
Page 597

The heading “Case for Importing and Exporting” should read “The Case for Importing and Exporting”.

Anonymous    Apr 01, 2009