I agree with iem. After having read the two sections in the book on untyped reports versus strongly-typed reports I was still left in the dark as to the merits / drawbacks of each. As well, I noticed with some annoyance that the two sections are often identical word-for-word, betraying an obvious cut-and-paste.
What's missing here is an exploration of the three available options: untyped, strongly-typed, and strongly-typed cached, answering the following questions.
1. At a theoretical level, what do these three things mean? There was some attempt to explain the difference between untyped and strongly-typed, but it was much too simple-minded. The exaplanation of what caching means was very clear.
2. Why would I want to / not want to use each of these options? The text simply says that I "probably want to" use strongly-typed reports, and tells me that caching is a good thing. Why, then, did Crystal even bother providing the other options, if I probably shouldn't be bothering with them? Obviously they must serve a purpose. Obviously strongly-typed reports are inappropriate in some circumstances, otherwise untyped reports wouldn't be offered. A discussion of things like ease of programming, runtime flexibility, resource consumption, etc. would have been appropriate.
B P Fraser
Sauder Information Systems