Chapter

Page

Where

Replace

With

Inside back cover

Book prices

Prices on books are incorrect. For example, the two Access 2000 Developer's Handbooks are listed at $54.99, where as the book the reader just bought cost them $59.99. Oops!

Frontmatter

Page xiiii

Replace all use of word "Appendicies" with "Appendices" or "Appendixes" (either one is acceptable, "Appendicies" is not). This one, unfortunately, broke after leaving our final edits.

5

126

First paragraph, second sentence

This form is totally self-contained and thus will work without any changes if you import it into any other database.

To use the form in another database, import the frmSQLScratchpad form plus the ControlResize, FormResize, and SectionResize class modules.

5

139

Figure 5.7 caption

you can include the CEO, Mary Jones, even though she has no supervisor.

you can include the CEO, Peter Jones, even though he has no supervisor.

6

270

Final line of the page

rst.PercentPosition

rst.AbsolutePosition

6

276

Listing 6.14

Entire listing, and remove WARNING on page 278. Unfortunately, interactions between ADO and Access seem to have changed since this chapter was written. ADOX is not required for this purpose.

Public Sub DemoParameters()

    ' Done without using ADOX

    Dim cmd As ADODB.Command

    Dim rst As ADODB.Recordset

    Dim prm As ADODB.Parameter

    ' Before running this procedure, open

    ' frmInfo and enter a value, like "Berlin",

    ' into the City text box, then tab off 

    ' of the text box.

    ' You must move the focus out of the 

    ' City text box in order for this to work.

    Set cmd = New ADODB.Command

    Set cmd.ActiveConnection = 

     CurrentProject.Connection

    cmd.CommandText = "qryCustCity"

    ' If you use adCmdStoredProc, 

    ' this won't work.

    cmd.CommandType = adCmdTable

    ' This next statement is actually optional.

    ' If you leave it out, ADO does it anyway.

    cmd.Parameters.Refresh

    ' Loop through the parameters

    For Each prm In cmd.Parameters

        prm.Value = Eval(prm.Name)

    Next prm

    ' And populate the recordset

    Set rst = cmd.Execute

    Do Until rst.EOF

        Debug.Print rst.Fields(0).Value

        rst.MoveNext

    Loop

    rst.Close

    Set rst = Nothing

    Set cmd = Nothing

End Sub

6

279

Table 6.10, 6th row, first column

adSeekAfterEq

adSeekLastEq

6

279

First paragraph, first sentence

If your index includes multiple columns, you must supply all the values in an array, which you can construct with the VBA Array function.

If you want to seek using an index that includes multiple columns, you can seek on just the first column using a single value. To seek on multiple columns, supply the values as an array (perhaps using the Array function to create the array).

Private Function IsLoaded(strName As String, _ 
 Optional lngType As AcObjectType = acForm) _

Private Function IsLoaded(strName As String, _ 
 Optional lngType As AcObjectType = acForm) _

7

422

2nd bullet point on the page, first line

the field you display must can

the field you display can

Remove the extraneous procedure, Private Sub ParseItems. At the beginning of the Property Let Text procedure, add the following line of code:

The previous erratum was incorrect. Instead of

Add the following line of code at the beginning of the Property Let Text procedure:

Code in HandleKeys method:

This replacement code:

The example may fail if you add a row to the first subform, and then immediately start adding rows in the second subform. Because code hasn't run to update the linking text box, the rows in the second subform will be orphaned. One easy fix is to call the Form_Current event procedure from the Form_AfterInsert event procedure, like this, forcing the text box to update as soon as you insert the new row:

Private Sub Form_AfterInsert()

    Call Form_Current

If your form contains controls that have negative offsets, the form resizing code can go into an infinite loop. I can't see how to make this happen (Access 2000 won't allow you to place controls at a negative offset), but one reader came across it.

To fix the problem, open the FormResize class module, find the GetControlInfo procedure, and locate the line:

.Name = ctl.Name

Immediately below that line, add these two lines of code:

In FormResize.ScaleFormContents, replace this code:

Cancel = msl.Cancel