โ Scribed by Warren Rachele
No coin nor oath required. For personal study only.
I have spent a lot of time studying this book. The early chapters are the best. The book needs work. It has a lot of valuable information, especially for a programming student who does not have much database experience. Unfortunately, it has a few glaring errors and omissions. The book has graphics that are labeled wrong. It refers to files on the accompanying CD that do not exist. I couldn't find an errata page on the Internet for the book. If the book were taken through a very serious editing process and re-published as a second edition, I might buy the new version. However, the quality of the writing, the overall poor quality of the binding, and the annoyances of being mis-directed make this book a poor comparison to "Delphi 4 Unleashed" and the Tomes of Delphi "Algorithms and Data Structures." Buy this book, only if you gave up trying to read database chapters in the Delphi 4 Unleashed. Also, be prepared to make a few mental jumps when you try to follow the projects.
๐ SIMILAR VOLUMES
Binding Unknown
This book is an expanded and updated edition of Clay Shannon's previous book, Developer's Guide to Delphi Troubleshooting, which received the following praise: "One specialized reference I found particularly useful was Clay Shannon's Developer's Guide to Delphi Troubleshooting, which is esse
This book is an expanded and updated edition of Clay Shannon's previous book, Developer's Guide to Delphi Troubleshooting, which received the following praise: "One specialized reference I found particularly useful was Clay Shannon's Developer's Guide to Delphi Troubleshooting, which is essen
Delphi Developer's Guide provides a solution-oriented approach to application development that uses the visual programming tools in Delphi for implementation. Covers design methodology as well as the software. Shows what the future holds for GUI application development. Explains how visual programmi
Is this a tome? I was expecting deep subject coverage. What we have instead is a reproduction of the API docs. Does that a tome make? I think not. What's missing? Complex examples. Real-world examples (who creates windows with API calls when we have TForm?). Undocumented insights behind