Errata for Certified Macromedia ColdFusion MX Developer Study Guide

As much as I’d like to be able to produce completely error free books, the reality of the computer publishing industry is that the pace at which books must be written and released makes this very difficult. And regretfully, my own books do have sporadic mistakes and typos scattered throughout them.

For the benefit of my readers, here is a current errata for Certified Macromedia ColdFusion MX Developer Study Guide. Feel free to print this page for future reference.

And as always, if you come across errors that I do not know about, please let me know. I’ll make sure they are added to this list, and will try to have them corrected in future reprints.

Original printing (426 pages, published January 15, 2003)

33Caution text, “1 to 5” and “1 to 4”.Should be: “0 to 5” and “0 to 4”
40Tip at top of page, “the TEMPLATE attribute”.Should be: the URL attribute.
44Table 5.3, RESET attribute.Default is YES.
44Table 5.3, TYPE attribute, second sentance.This belongs in the FILE attribute.
57Code example, CFQUERY tagMissing closing tag.
62Code block, CFQUERY name attributeShould be: Users
63Final bullet itemShould be: IS NULL
63Last bullet item.Should be: IS NULL
73Line of code in tip at bottom of page.# is extraneous and should not be present.
74Code snippet above last tip, middle line.Extraneous space between # and CountryID
79Second note, second line, words “the browser collects”.Should be: “ColdFusion collects”.
95CautionThis no longer applies as of CFMX.
112Note, second line: a,,bShould have s apace in between the commas: a, ,b
121First paragraph, text “which places values at the beginning or end of the array”.Should be: “which places values at the end of beginning of the array”.
128Final code snippet, third line from the should be in quotes: “email”
139First line following first script block: unoShould be: In Spanish, the number one is ‘uno.’
140Note, send line: is or ifShould be: is or lt
145Question 3, code snippet.Hyphens before and after “World” and “Hello” should be removed.
156Note, text “when one record”.Should be: when one recordset
157Code snippet at top of page, query name in CFOUTPUT.Should be: qItemsInStock
160Second note, words “READ COMMITTED”.Should be: “READ_UNCOMMITTED”.
166Question 4, answer B.Should be: “REPEATABLE_READ”.
175Question 2, answer A.Should read “Use it twice and subtract the first reading from the second”.
178Table 21.2, description of variable Error.GeneratedContent.Word “request’s” is repeated, should only appear once.
178Table 21.2, second sentence of description of variable Error.HTTPReferer.Should read “This will be an empty string if there is no referrer”.
181Tip at bottom on page.The tip only applies to ColdFusion 5 and earlier, it does not apply to ColdFusion MX (ColdFusion MX locates the best match regardless of sequence).
204Question 3, answer A.Missing ATTRIBUTES. prefix.
204Question 3, answer D.Missing trailing “>
210First code snippet, first CFSET tag, GetParentTagVarsShould be: stGetParentTagVars
217Section “Variable Parameter Lists, 3rd line, text: tab-basedShould be: tag-based
218Code example at top of page, second line.Should read: function functionName()
228First line following the note, text “that they need be”.Should read: “that they need not be”.
230First bullet, text “an invoke”.Should be: and invoke
2302nd to last paragraph: syntax, and methodsShould be: syntax, methods
233Question 23rd answer should be answer C.
239Sample question 1, third answer.Should be “C”.
241First line under “Using Java” heading, opening words.Should read: “ColdFusion runs on underlying Java technology”.
248Final paragraph, first sentence.Should read: “The <CFXML> tag creates a new XML Document Object”.
250<CFSET> three lines from bottom of page.Should read: <CFSET[1].xmlchildren[1].xmltext=”Homepage”>
260Bulleted list, 4th bullet.Should not be part of bulleted list.
263Using DataGlue section, first line, text “bylooping”.Should be: by looping
290Final code snippet, FILE attribute.Should have a fully qualified file path.
290Paragraph above the Caution, sentence “For example”.Should be: For example, MODE=”755″ gives rwxr-xr-x permissions (owner=read/write/execute, group=read/execute, other=read/execute).
291First code example, 7th line, <CFSAVECONTENT>.Should be: </CFSAVECONTENT>.
291First code snippet, first line of code.Missing = after VARIABLE
292Second caution.This no longer applies as of CFMX.
292Final two lines, FILE prefix.As of CFMX should be: CFFILE
2934th bullet, FILE prefix.Should be: CFFILE
2932nd tip, FILE prefix.Should be: CFFILE
298Second code block, sixth line, text “aargs[1]”.Should be: aArgs[1]
345First note, opening words.Should read: “Joins are logical entities,”.
358Bulleted list, 4th bullet.Should read: Unique constraint values may be reused.
397Chapter 12, answer 2.Correct answers are “C, D, and E”. (B is incorrect).
399Chapter 16, answer 3.Incorrect explanation text, should be: As no break statement is used, both lines will be executed.
400Chapter 20, question 3.C is also correct as ColdFusion Studio can display web browser pages.
401Chapter 24, answer 1.Correct answer is D.
402Chapter 27, answer 1.Should be “C and D” (text is correct, answer letters are incorrect).
403Chapter 28, answer 2, 4th line: CFIMPORTShould be: CFINVOKE
404Chapter 33, answer 3.Should be “A and D” (text is correct, answer letters are incorrect).
404Chapter 31, answer to question 3.A C and E are correct.
405Chapter 34, answer 2.Correct answer is C.
405Chapter 36, answer 1.Correct answers are B and C.
407Chapter 44, question 1.Correct answer is A (as multiple conditions are being checked, not multiple values).