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.
| Version |
Location |
Description |
Submitted By |
Date Submitted |
Date Corrected |
| Printed |
Page 3
last paragraph, first sentence |
"...you're reading to move on ..."
should be "...you're ready to move on ..."
|
Anonymous |
|
|
| Printed |
Page 17
Figure 1-10 caption |
"When you're designing a form, ..."
change to:
"When you're designing a table,..."
|
Anonymous |
|
|
| Printed |
Page 25
1st paragraph, 3rd line |
"...Ed's Roadside Dinner..."
"Dinner"-->"Diner"
|
Anonymous |
|
|
| Printed |
Page 30
Section # 3, last sentence |
"... then click OK."
Figure 1-3 doesn't show an "OK" choice to click.
Might be clearer to move figure reference to the point above, so step #3 reads "Choose a folder (Figure
1-3)" and remove it from section below.
|
Anonymous |
|
|
| Printed |
Page 32
Figure 1-4 caption, second sentence |
"... jump from a list of products to a list of customers..."
Figure 1-4 doesn't show either Products or Customers.
Might be clearer to reword second sentence from "You can use the ?" to "For example, you can use the ?"
|
Anonymous |
|
|
| Printed |
Page 42
Table 1-2, Key = Esc, second sentence |
"...Once you move to the next cell, change is applied."
qualify "change" with "your change" .
|
Anonymous |
|
|
| Printed |
Page 66
Note (at top) |
Replace "you probably need two" with "you probably need two or three"
|
Anonymous |
|
|
| Printed |
Page 94
Section 2, first paragraph |
Replace "a single Name field" with "a single ContactName field"
|
Anonymous |
|
|
| Printed |
Page 97
Last paragraph |
Replace "It's relatively uncommon for two customers to share the same address" with "Most customers have
separate addresses"
|
Anonymous |
|
|
| Printed |
Page 98
Tip (at top) |
At end of second sentence in Tip box, add "on a scrap piece of paper."
|
Anonymous |
|
|
| Printed |
Page 123
First sentence in "Find and Replace" section |
In first sentence of sidebar, change "The search feature" to "The Find feature"
|
Anonymous |
|
|
| Printed |
Page 177
#8 |
The description of how to connect the two tables is the opposite of the header for this item. The header
says drag from parent to child ... the example drags from child to parent.
RESPONSE: This is technically true, but the steps cited are still correct and it doesn't warrant
replacing the figure. Consider updating the figure next edition.
|
Anonymous |
|
|
| Printed |
Page 181
second bullet point |
"Once this record's removed, you're left with ..."
change to:
"If this record were removed, you'd be left with ..."
|
Anonymous |
|
|
| Printed |
Page 190
Caption for fig. 5-12. |
Second sentence of caption, "One links students to classes, and the other links teachers to classes," does not belong here. Figure 5-12 illustrates the procedure for setting sort order of lookup list, using the "Manufacturer" field of the example bobble-head doll database.
Note from the Author or Editor: p. 190, caption for Figure 5-12, remove "One links students to classes, and the other links teachers to classes."
|
David Scheu |
Sep 01, 2009 |
|
| Printed |
Page 196
second sentence |
"... Access gives you two ways ..."
It appears that multivalue fields are not included in the For Starters edition. If this is the case,
change "and Access gives you two ways to deal with them" to "and you can use junction tables to deal with
them"
|
Anonymous |
|
|
| Printed |
Page 199
Note section, first line |
"... using a multi-value lookup field ..."
A multi-value lookup field hides the one-to-many relationship that exists. While this might make working
in a table easier, it makes working with the data more difficult.
Remove the Note box. I don't think this is discussed in the example (and multivalue fields aren't
described in the book anyway).
|
Anonymous |
|
|
| Printed |
Page 214
first sentence in first paragraph under Creating a Query in Design View |
"The best starting point for query creation..."
Change to "The best starting point for creating most queries is Design View."
|
Anonymous |
|
|
| Printed |
Page 221
Bamker's Roundig, 2nd column, 3rd line |
"that" s/b "than"
Note from the Author or Editor: p. 221 "more often that you round down" should be "more often than you round down"
|
Leo J.Carling, III |
Mar 05, 2009 |
|
| Printed |
Page 229
2nd paragraph under Queries and Related Tables |
"... that pulls columns from two tables ..."
change to:
"... that pulls columns from two or more tables ..."
|
Anonymous |
|
|
| Printed |
Page 232
Note section |
In note box, change "many tables share a common ID field" to "many tables have a field named ID, but these
fields aren't related in any way." Change "just remove it before adding the join you really want" to "just
click to select it and press the Delete key to remove it."
|
Anonymous |
|
|
| Printed |
Page 236
first full paragraph, second sentence |
Change "Any orders that aren't linked to a customer record appear at the bottom of the list, and have ?"
to "Any orders that aren't linked to a customer record have ?"
|
Anonymous |
|
|
| Printed |
Page 243
Figure 6-22 caption |
In figure caption, change "This query shows two fields straight from the database (ID and Name), and
adds ?" to "This query shows the ProductName field straight from the database and adds ?"
|
Anonymous |
|
|
| Printed |
Page 246
last sentence |
Change "the new date becomes" to "the ExtendedDeadline date becomes"
|
Anonymous |
|
|
| Printed |
Page 248
next to last line on page |
Change "However, you can join text together " to "However, you can join text together using a process
called concatenation."
|
Anonymous |
|
|
| Printed |
Page 255
#2 |
Change "Adding multiple tables" to "adding more than one related table"
|
Anonymous |
|
|
| Printed |
Page 260
#10 |
Change "UpdateProductPrices" to "RaiseProductPrices"
|
Anonymous |
|
|
| Printed |
Page 262
Note |
Change note text to "You shouldn't try to copy AutoNumber values in an append query, because you have no
way of knowing if these numbers are already in use. Instead, leave the AutoNumber field out so Access will
assign new numbers."
|
Anonymous |
|
|
| Printed |
Page 268
#6 |
"If you used the asterisk (*), you'll see the full information for each record."
Replace "the full information" with "all the fields"
|
Anonymous |
|
|
| Printed |
Page 273
Figure 8-1 caption |
"Ordinary printouts are ..."
change to:
"Ordinary datasheet printouts..."
|
Anonymous |
|
|
| Printed |
Page 277
Up to Speed |
Change "heavy-duty filtering or sorting" to "heavy-duty filtering" and at the end of the first paragraph
add "However, the sort order you use in the query won't affect the order of records in your report."
|
Anonymous |
|
|
| Printed |
Page 281
Layout View bullet |
"... and rear-
range..."
change to:
"... and re-
arrange..."
|
Anonymous |
|
|
| Printed |
Page 283
Last paragraph, first sentence |
"After you've closed your report..."
change to:
"If you've closed your report..."
|
Anonymous |
|
|
| Printed |
Page 303
Last paragraph |
Replace the bottom paragraph on page 303 with this corrected text "Initially, the records in a report have
the same order as the underlying table. Typically, this means the records appear in the order you added
them. Reports ignore any sorting that you've applied to the table in Datasheet View." On the next page,
change "Either way, you can apply formatting" to "You can apply sorting"
|
Anonymous |
|
|
| Printed |
Page 311
Figure 9-4 caption |
In Figure 9-4 caption, change "form" to "report"
|
Anonymous |
|
|
| Printed |
Page 326
The Form Wizard, #2 |
"... choose the table you want to use."
change to:
"... choose the table (or query) you want to use."
|
Anonymous |
|
|
| Printed |
Page 328
Figure 9-12 caption |
"...then click the > button..."
change to:
"... then click the > button (or double-click the field)..."
|
Anonymous |
|
|
| Printed |
Page 334
|
The heading “Case for Importing and Exporting” should read “The Case for Importing and Exporting”.
|
Anonymous |
|
|
| Printed |
Page 334
last sentence |
Change "because it involves" to "because it often involves"
|
Anonymous |
|
|
| Printed |
Page 335
Note, 2nd sentence |
"The original copy always remains..."
change to:
"The original always remains..."
|
Anonymous |
|
|
| Printed |
Page 340
Timesaving Tip |
Remove sentence "However, it works only if you're copying a complete table (or other object), not a
selection of rows."
|
Anonymous |
|
|
| Printed |
Page 341
1st sentence under #5 |
"...to create random field names..."
change to:
"... to create arbitrary field names..."
|
Anonymous |
|
|
| Printed |
Page 593
The highlighted note |
The book says "In order to successfully use a password with a back end database, you must apply the password before you split the database. Otherwise, access won't store the password in the front end and the linked tables won't work."
This is not true. When you create a database, add a password, then split the database. The password is attached to the front end file, not the back end file. Users can still update the tables by opening the back end without a password.
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 |
Jun 20, 2008 |
|