The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
| Version |
Location |
Description |
Submitted By |
| Printed |
Page 29
Figure 1-10 |
Figure 1-10 shows 14th (= last) record of the found set. Caption says: seventh.
|
Meindert Meindertsma |
| Printed |
Page 38
Figure 1-18 |
The names in the figure are supposed to be sorted by Last Name and then First Name. But, Niki Sanders comes before Micah Sanders.
|
Anonymous |
| Printed |
Page 57
last paragraph |
The OR should read AND in the two sentences.
|
dieudonné |
| Printed |
Page 323
First paragraph (handy cheat sheet) |
Susan Prosser/ Geoff Coffey,
I am confused and getting more so....
(Chapter 7:Adding Multiple Tables and Relationships; p. 323)
In creating the relationships, we are pointed to use the 'handy chest sheet'.
I think one of the 'drags' in not very clear. Something is missing (?)
If, as you state in the book, "the stuff before "::" is the table name, and the stuff after is the field name", then the 4th item is incomplete. It is missing information as to what table the field Invoice ID from the Invoice Payments table should be dragged to.
• Drag Invoice Payments::Invoice ID to Invoice ID.
Q.: Does this mean to drag the field Invoice ID to itself?
Cordially
Fernando Goncalves
Toronto, Canada
FGoncal197@aol.com
|
FernandoJorge |
| Other Digital Version |
326
Errata page on this website |
In the errata page for this book on this website, the errata item for page 326 under "Note from the Author or Editor" the first sentence should read (instead of the word "graph"):
"1. p. 326, second paragraph, third sentence should read..."
Also, on the errata page for this book on this website the errata item for page 714, in the Location column the word 'Figure' is misspelled as 'Figue'.
|
Ronald Ogg |
| Printed |
Page 549
2nd paragraph |
2nd paragraph, 2nd and 3rd sentence:
"If the record is already open, then it does nothing...It just locks the record if it isn't locked already."
This seems to conflict with the 4th sentence which says:
"But if the record is already open...then you get a record locking error."
What DOES it do if the record is already open?
|
Jack Leonard |
| Printed |
Page 573
Figure 14-18 |
Figure 14-18 shows the Send Mail Options Screenshot whereas the text relates to the Execute SQL script step.
|
John Wolff |
| Printed |
Page 650
'Warning' - last paragraph |
On page 650 the 'Warning' paragraph says
" Make sure you don't forget your Full Access password. FileMaker uses industry-standard and ultra-secure techniques to manage passwords, you simply have no way to bypass them. Filemaker Inc may be willing to change the password in the file, but the process takes several weeks and is not guaranteed."
This statement make be technically correct but is seriously misleading.
Leaving aside the the matter of "ultra-secure techniques", which is certainly open to question, while it may be true that one cannot "bypass" Filemaker passwords it is a matter of minutes to download readily available software that will instantly disclose all the passwords in use in a particular file, as I found out when I mislaid a file's passwords and was given no hope from Filemaker.
All it takes is to Google 'Filemaker Pro password recovery' and there is a variety of options.
I can understand why Filemaker might not want this gap in file security to be widely known, but it is definitely to the benefit of developers to know that they should seriously explore external authentication options if they wish prevent unauthorised access to the 'innards' of an application.
Surely an 'independent' manual such as the 'Missing Manual' should include this information amongst its other 'words to the wise'?
|
Anonymous |
| Printed |
Page 682
Insert titled " Where's My Style" |
The text explains that there is no simple way to export to a format external to Filemaker without loosing text attributes. However, if you use the PDF save function, this essentially provides an additional simple export method that easily saves text with all its formatting intact. This method is described correctly on page 663. Maybe the paragraph could include a reference to the PDF save function.
I can't figure out why the programmers would put that function in a separate menu item - strange, or at least not include it in the export function. OK, perhaps its because so you can't choose the fields the same way, but you can easily create a layout with just the fields desired for "exporting". Then once you have created the PDF file, you can cut & paste etc. and still have all the formatting intact.
Please let me know if I am missing something....
|
Dave |
