Noticed a discrepancy with the Shipping Addresses table
Page 59, fsubShippingAddresses. Refers to the field ShipAddress. This field is not shown on page 23, although there is a reference to it "… and a set of address fields. Although the address fields could have the same names as the corresponding fields in tblCustomers, I like to prefix their names with "Shipping" or "Ship" so that if the billing and shipping addresses are combined in a query, we won't need to use the table name prefix to distinguish between them." Table is shown in Figure 1.19. Image of the table in design view does not show ShipAddress.

In Toy Workshop (Forms Start) download, the field ShipAddress is not listed with the table. In Toy Workshop (Forms Finish)download it is. Not a big concern, just thought it should be mentioned.

Sue


Sue

You stated that "Refers to the field ShipAddress."

I don't see the error here that you are referring to . I don't see a specific reference to a field named ShippingAddress on page 59.

The information in figure 1.19, on page 23, does show the field ShippingAddressID which I am sure is the field to be used. And the field that is shown in figure 2.20 is clearly labeled as the Shipping Address Identifier. And the text in the 2nd last paragraph on page 59 does say "Drag the AddressIdentifier..."

Since this is a new publication, I am pretty certain that we both have the same edition. Can you be more specific about the location of this reference to the field ShipAddress?

Sue, there is no doubt in my mind that you are exactly right.

The statement on page 59 "The third subform needed for frmCustomers is based on tblShippingAddresses." clearly implies that the form is bound. Therefore since Figure 2.20 displays "ShipAddress" in a textbox, that textbox is bound to a field named ShipAddress from tblShippingAddresses.

However, ShipAddress is NOT listed as a field in tblShippingAddresses in Figure 1.19. But ShipAddress is listed as a field in Relationships windows shown in Figure 2.1. And as you correctly pointed out. "In Toy Workshop (Forms Start).mdb the field ShipAddress does not exist as a field in tblShippingAddresses (and in fsubShippingAddress). In Toy Workshop (Forms Finish).mdb the field ShipAddress does exist as a field in tblShippingAddresses (and in fsubShippingAddress)."

So, tblShippingAddresses must have been changed (by adding the field ShipAddress), but that change was not mentioned in the text of the book.

Terry Waltz

Thanks for pointing that out, tlwaltz.

I should have looked further down the Figure 2.20. I stopped looking at the first two fields.

I now see the field (4th) being referenced. And Figure 1.19 shows ShipDepartment vs. ShipAddress. Figure 2.1 also shows ShipAddress, as so some subsequent Figures of subForms.

So it would seem that Figure 1.19 is the one in error. Other than in Figure 1.19 there seems to be no reference to ShipDepartment. In Figure 1.19, ShipDepartment should be ShipAddress.

Guess this should be added to any errata document that follows, and corrected in next publishing. Good catch Sue!

Hi Terry and Bob,
Glad you could confirm the minor problem with tblShippingAddresses. Since, I'm not a programmer by profession or nature, it is sometimes easier to spot something amiss because I'm struggling with it. It is exciting to finally get some areas of Access that have confused me cleared up.

Sue

Sue

I think the basic problem here is that many of the tables in the sample Toy Workshop database go through changes as the chapters progress, and various techniques are illustrated, so they won't necessarily look the same in Chapter 4 as in Chapter 1 (for example). In Fig. 1.19 there is no ShipAddress field in tblShippingAddresses, but it is there in Fig. 2.20 later on.

Helen Feddema
Kerhonkson, NY
[email protected]
http://www.helenfeddema.com
Read Woody's Access Watch
http://www.woodyswatch.com/waw/

I'll keep the various permutations of the tables in mind. Right now, I'm overcommitted, so going through the book is progressing slowly. I do have some questions, but want to make sure I've really gone through the code and Access/VBA help before asking them. Just asking won't be as helpful.

Sue

Sue