Errata for Professional Active Server Pages 3.0   [ISBN: 1-861002-61-0]

Wrox Logo
Chapter Page Details Date Print Run
  0 Using RUNAT=CLIENT in a SCRIPT Element
Note that in Windows 2000 RC2, the ASP interpreter will not allow the
RUNAT attribute in a SCRIPT element to be set to CLIENT.

Using SCRIPT RUNAT=CLIENT produces the error message:

Active Server Pages, ASP 0120 (0x80004005)
Invalid Runat attribute
The Runat attribute of the Script tag or Object tag can only have the value
Server.
14-Feb-00 1
  4 Cannot run IIS 5.0 and ASP 3 on Windows 9x
On Page 4 of the book we state that "You can run IIS5 with ASP3 on Windows 9x". This is not possible, and is not likely to be possible in the future.
14-Feb-00 1
  5 Introduction - missing page
The missing page can be viewed at this url:
http://www.wrox.com/consumer/errata/2610/2610_Intro_Page5.html
27-Mar-00 1
  60 Using multiple images to submit forms
On page 60 you say that "input buttons of the type SUBMIT and IMAGE actually do submit the form to the server, and their value attribte is included with the values of other ontrols on the form provided we include a NAME attribute in the HTML definition"

This is not true for inputs of type IMAGE. These inputs submit not a NAME=VALUE pair but the coordinates of where in the image the user clicked as in E.X=xCoordinateValue&NAME.Y=yCoordinateValue. Your example code the bottom of page 61 works with a SUBMIT button as in "If Len(Request.Form("btnNext")) then ... ". But this must be written as "If Len(Request.Form("btnNext.x")) then ... " for an IMAGE input.
14-Feb-00 1
  90 AppendToLog method

There is an error in Chapter 02, page 90. "AppendToLog" method link is on
the main "Response Object" page, NOT the "Request Object" page.
14-Feb-00 1
  169 URLEncode examples
Bottom of 169 & top of 170.

The URLEncode function as well as the HTML encode functions are using a
string literal for the variable name instead of the variable name itself.

Also, on the link itself, you have coded as:
<A HREF="<%= strURL %>"><% = strValue %></A>

It should be coded as:
<A HREF="<%= strURL %>"><% = strLink %></A>

based on the context of the example.
14-Feb-00 1
  197 Scripting Objects Constants
There are some errors in the Scripting Runtime Library.

On page 197 we have 'Network' defined as 3, with a comment stating this
isn't predefined. It's now in the type library, but as 'Remote'. This
also affects Appendix B (page 114).

On Pages 200 and 205, the one of the Attributes values is now different.
'Alias' is now defined as 1024. This also affects Appendix B (pages1145
and 1147)
14-Feb-00 1
  211 Chapter 5
In the section 'Opening a File Object as a TextStream Object', the three
JScript examples should use the OpenAsTextStream method rather than the
OpenTextFile method.
14-Feb-00 1
  360 An "=" that shouldn't be there
There seems to be an error on page 360, in the second shaded box of code.
There's an "=" operator that should not be there.

The code as listed incorrectly is:

cmdUpdate.Parameters.Append = _
cmdUpdate.CreateParameter("@Percent", adCurrency, adParamInput, , 10)

Since Append is a method of the Parameters collection, there should not be
an "=" operator between Append and cmdUpdate.

Here's the corrected code:

cmdUpdate.Parameters.Append _
cmdUpdate.CreateParameter("@Percent", adCurrency, adParamInput, , 10)

This same error is repeated again on the next page, 361.
14-Feb-00 1
  381 Incorrect connection string
On page 381, the line of coding demonstrating how to set up a data shaping
connection string is slightly incorrect:

strConn = "Provider=MSDataShape; Data=" & strConn

There should not be an = sign after the word Data, i.e.

strConn = "Provider=MSDataShape; Data " & strConn
14-Feb-00 1
  381 Incorrect connection string
On page 381, the line of coding demonstrating how to set up a data shaping connection string is slightly incorrect:

strConn = "Provider=MSDataShape; Data=" & strConn

There should not be an = sign after the word Data i.e.

strConn = "Provider=MSDataShape; Data " & strConn

15-Nov-99 1
  451 Small Typo
At the bottom of the page, on the line just under the code snippet, the 0 should be a 1.
23-Feb-00 1
  460 Error on page 460 nodValue property
On page 460, at the paragraph that reads: "Here we've just used the
nodeValue property, and this is a Microsoft extension to the DOM." This
statement is inaccurate. The nodeValue property isn't an extension to the
DOM, according to Microsoft (cf. XMLDOMDocument Object, extensions to the
DOM are marked with "*" [MSDN Library, October 1999]), and according to the
W3C (cf. http://www.w3.org/TR/REC-DOM-Level-1/level-one-core.html).

Moreover, the paragraph continues "The W3C specification doesn't actually
give a simple way to access the value of a node - you always have to
traverse to the child to access the associated TEXT node. Microsoft decided
that one of the most common actions would be to access the value of a node
to get at the text int contains, so they introduced the nodeValue property.
This handles the child TEXT node for us." I believe that the author was
referring to the nodeTypedValue property instead of the nodeValue
property.

Therefore, I believe that the paragraph should be rendered as such: "Here,
we've just used the nodeValue property. The W3C specification doesn't
actually give a simple way to access the value of a node - you always have
to traverse to the child to access the associated TEXT node. Microsoft
decided that one of the most common actions would be to access the value of
a node to get at the text in contains, so they introduced the
nodeTypedValue property. However, the nodeTypedValue property also seems to
retrieve the TEXT node of all of the subtrees of a given element, and for
that reason, it was not used in the above example."
14-Feb-00 1
  631 Reference to BookData
When you create the Business Logic project, you also need to create a reference to the BookData DLL.
10-Dec-01 1
  816 NDS description
On page 816 we incorrectly specified that Novell Directory Services were not LDAP compliant. This is incorrect.
31-Mar-00 1
  1046 Thread Gating
On pp. 1046-1047, I described Thread Gating, a new feature in IIS 5.0,
which attempts to dynamically tune the number of ASP worker threads
actively executing. After the book went to press, this feature was disabled
by default, as experiments on microsoft.com revealed that thread gating
hurt performance there. On other sites, it helps performance. However, we
decided to err on the side of caution and turn the feature off in IIS 5.0,
so that the thread scheduling behavior more closely matched that of IIS
4.0.

To enable thread gating,
cscript \inetpub\AdminScripts\adsutil.vbs set w3svc/AspThreadGateEnabled
true

14-Feb-00 1