Software Books

Extending the hand dealt to you by the development package is where the quality programmers are separated from the mere developers; often the difference between an adequate product and a great one. If you are a developer using Delphi and want to advance to a higher level of production, this book contains the necessary boost. Anyone moving into Delphi component creation will find it essential. From properly choosing components from the Delphi Visual Component Library (VCL) to building your own components and interfacing with OLE and COM, most of the major topics are covered in detail, with sections of example code to really drive the message home.
The book starts off with a brief explanation of the models used in Delphi, basic concepts of a component, and the analysis and design of new components. This is followed up by an examination of Implementation Details, the fundamentals of polymorphism, virtual methods, exceptions, RunTime Type Information (RTTI), streaming, messaging, OLE and COM interfaces, and optimization techniques. "Design Time Support Tools," opens with an overview of the Integrated Development Environment (IDE) and emphasizes the interface issues. Danny Thorpe wraps it all up with chapters on property and component editors, and experts and add-in tools.
This book contains many insightful points. The chapter on virtual methods and polymorphism contains the best explanation of the implementation details of virtual methods that I have ever seen. This chapter could serve as a reference in any study of object-oriented programming. I've incorporated many of these points into my own training course. As one whose main approach to OOP has been via C++, I found this material invaluable when teaching a course in advanced Delphi recently. The clear descriptions of the underlying implementation distinctions between virtual and dynamic methods may save you in the area of performance. Knowing and understanding why virtual methods will defeat the smart linking of the Delphi compiler/linker can reduce the size of your EXE.
When I am presenting exceptions and exception handling to experienced programmers, they always ask the following question: "What is the real difference between this and how we have traditionally handled errors?" In only a few pages, the author answers this question and puts forward two lists, "Rules of Thumb for Implementing Exception Handlers" and "Rules of Thumb for Raising Exceptions"; solid advice for both developers and educators who develop developers.
Optimizing code when there is "abundant" stack space (surely a hint of heaven!), multiple threads and different system-defined string types differ from traditional tricks. These topics are all covered in the chapter on optimization. Just because this space is available is no reason to misuse it. Knowing that the stack will never shrink over the lifetime of the thread should force you to rethink overuse. Understanding that long strings are allocated on the heap rather than the stack should cause an occasional re-examination of approach. It is also gratifying to see that there is also a short section on sledgehammer techniques, or put another way, "genuinely useful hacks."
There is also an occasional sweet sprinkle of humor. From polymetamorphicdata (care to guess what that is?) to TypInfo ("tip info") and GUID ("gwid") the jokes are appropriate and blend well into the message. However, they are grains of seasoning rather than the bulk of the flavor.
Delphi is a development environment that provides the opportunity to do many things quickly and efficiently. Add in a copy of this book and you are ready to harness the true power of Delphi by creating your own components and pushing things to the leading edge of software creation. Some sections can be read and appreciated just for their insights into object-oriented programming and design.

Published in Journal of Object-Oriented Programming, reprinted with permission.

This is purely a Delphi programmer's guide, but it unquestioningly well written, informative, and well-rounded: Anyone seeking to learn how Delphi's VCL component libraries work, how to development components of their own, or how to extend Delphi VCL components already available from Borland or third parties, should read this book. There is simply nothing else that comes close.

Mr. Thorpe's writing style is clear, concise, and does a great job of exploring the topic at hand. Any competent Delphi programmer will be well capable of undertaking VCL development on their own if they have this book at their side. One point to note about this book is what used copies go-for on Amazon.com (and elswehere): I typically see prices of between $50 and $100, even though the book was first published about 10 years ago. How many other technology books, particularly for a specific software technology, remain in such high demand after such a long period of time?

"Delphi Component Design" was written for the VCL [Borland's Acronym for "Visual Component Library"] as it was implemented in Delphi 3.0 - back in the mid to late 1990's: the implementation of VCL it describes is still the foundation underlying VCL as implemented in Delphi today, and is close enough to the modern implementation to still be a very useful text. However, since Delphi's product direction is to pursue .NET as opposed to enhancing the older VCL, the book's usefulness is limited to those who are seeking to maintain or enhance existing Delphi VCL-based applications. Even though I no longer work in Delphi, I still find myself called-upon often enough for Delphi support that I'm not going to give up my copy of "Delphi Component Design" quite yet - even despite the used copy prices I see!

This guys are crooks. They advertise a book they DO NOT have, get your money and never reply to your e-mails.

The book is supposed to be great, by the way.

The book is a breath of fresh air and covers a good basic foundation: attitudes of programmers, basic structures of OOP with objects:- various virtual methods, basic construction of building blocks, streams, other forms of communication and a few peculiar things to watch out on. I personally have no interest in databases were some may have. 32 bit is the way to go as I can now see access to the windows API with the assistance of the book and Delphi Pro.
Danny points out its not necessary to understand every base object behind the object you are building off from.
This is true if you wish to add a minor adjustment to a component. But this I believe this is a major miss conception if you are building a new and different component. And for this purpose the book dose not begin to address threading, what is happing in TObject, as TObject is not in Delphi Pro to view and is the fundamental object that every object is built from!!!!!!. This is no different than the Pascal 7 days when every one wanted to read the OOP code for them selves at an enormous cost for a copy.
I'm not saying the book should cover the windows API as that's another subject on its own, but how a action is handled through the Objects, or how a windows event is managed though OOP:- draw, mouse button.....
I need a book that should cover enough to be able to install an object into a base object like a speed button into an editor or a listbox connected to a speed button so something like TCombobox or TGraph is understood how each piece interacts and is constructed together as a unit. When the OOPer's get hold of this understanding the tools for Delphi could become available will become limitless to the users. VB definitely has this advantage over Delphi today because we do not understand enough to create something different or new. Give it another go Danny with an extra book, as it is easy to understand what you have written, be cursus to get such a difficult subject right. And you have made a breath of fresh air already into the subject that is very useful to those that have read your first book but some of us need to go further.

This book is all about what goes behind the curtains. If are a crazy developer like me and interested in knowing how Delphi designers implemented different mechanisms such as WIndows messaging OLE COM this title is a must

Mr. Bartle's writing is precise and his facts carefully researched, even the ones he experienced himself. This is a huge, superbly constructed history of the tools and philosophies developed over the years in experimental and commercial development of online virtual worlds. Because of Mr. Bartle's personal knowledge as a long-time designer and his sharp memory for the significance of trends and details, this book will raise anyone's appreciation of whatever virtual worlds one comes across on line or on disk, whether they be famous commercial ones or those developed by enthusiasts for their own pleasure. I would think it would be a must read for gaming students. What a grand, satisfying, fascinating book! And when one considers that this exciting history is only the beginning of VW development... Wow!

This book taught me the theory behind Virtual worlds and I beleive nearly everything I read in this book.

I didn't simply believe everything because it was a published book, I beleived it because Richard used examples from real games. With all the experiance Richard has you would expect him to have learnt everything the hard way, he has but he's also smart enough to realise that sometimes you can learn from others mistakes instead of making them yourself.

The book is aimed at the 'Dungeons and Dragons' (and most of his examples are) type of game but there is no reason the information cannot be used in other genres.

The most amusing part is how right he can be.
Richard states that 'you cannot allow players to carry items over from the Beta testing to the online game, even though your players will try to convince you otherwise'; something I didn't really think and didn't really agree with.
My family and I were all about to join 'Pirates of the Caribbean' when it started; when the announcement was made that players form the Beta test would be allowed to keep items my daughters asked what a Beta test was, I explained and now they don't want to play as they consider that to be cheating. We have all decided not to play.

Learn from others (like Richard) or pay the price.

James

Covers all the aspects of virtual worlds from a psycological perspective; the intentions, the types of virtual worlds.
Doesn't include indepth technology and the development issues related to designing virtual worlds
Good primer on virtual worlds.

To begin with, this book is not a programming book. There is no code, no discussion of VRML, MPEG-4, or X3D. Instead, this book stands back and takes a "big picture" look at the design of a virtual world from the viewpoint of systems engineering, social engineering, philosophy, history, and psychology. Ethical considerations are even tossed in for good measure.
The book starts out with chapters on the history of virtual worlds and the cultural influences that affected their characteristics. Next, there is a fly-over view of the "production line" of building a virtual world. Bartle then turns his attention to the players - who they are, what they want, and how a virtual world can meet their needs. World design is examined from the standpoint of virtual geography, virtual world citizens, and finally the physics required to implement your world. Chapter 5 is about the specific sociology and physiology of the virtual world - skill levels, individual characteristics, how virtual inhabitants divide themselves into groups, combat, and even the meaning of death in the virtual world. The final three chapters are very philisophical in nature. Chapter 6 is basically a liberal arts syllabus through the prism of virtual world design. The last chapter, on ethical considerations, talks about censorship, and also looks at the player as a person and how game playing in virtual worlds can hurt more than help some kinds of people, particularly those prone to addiction.
Bartle's social commentaries may be a bit long-winded for some people, although I found them interesting. Some readers may also be somewhat frustrated by the fact that the book talks more about what can go wrong in the design of a virtual world - overly complex and static story arcs, characters that players do not get invested in, characters in which players get too invested, etc - than what can go right. I really enjoyed the book, mainly because it moves the focus of the potential virtual world designer from the artistic and technical viewpoint to the player's viewpoint - why they plays games, and why a player would pick your game versus someone else's game.

You're getting it straight from the horse's mouth since this book is written by the grandfather of the modern MMORPG.
Rest assured - if you are a game designer, developer, or just love reading about game theory, this book is worth every penny.

I have read many other books on the subject and not one of them are packed with as much depth, knowledge, and wisdom. Bartle covers every avenue that a designer needs to consider in order to be successful. This book will help you and your team create an active, emergent virtual world.

As a game developer, I learned many valuable lessons on what made other games lose subscribers, or worse -- catastrophically fail.


Richard Bartle's writing style is very creative and detailed, and like his games, it gives you the 'just one more page' syndrome. For example, in this book it mentions how often a player must be rewarded in order to retain interest. He uses this same technique for writing by giving you something insightful to read atleast every 10 pages.


Bartle has covered all the bases. Designing Virtual Worlds is a great book, very entertaining. I give it 5 out of 5 stars - a must read.

More than 700 well-written pages packed with valuable insights, and it still leaves you begging for more.

I have to say, this book is awesome. It taught me how to build models and understand why I am doing what I am doing. I use it all the time and hopefully he will release a new version for us folks who will outgrow this one. Covers all bases and it's worth 2x what I paid for it...

this is very good because it teaches step by step and it makes sense too.

The book is a very clear, step-by-step of all the processes involved in making a game character leading up to the animation. The animation is covered but not in as much detail. Everything else is though, including the awesome rigging machine which comes with the book.

Its refreshing to see that someone wasnt limited by a publisher to keep the book size down, and he obviously was able to take his time really illusrating every step.

Its a great book.

This is my first time to write this kind of review, therefore, I don't know how to do a good one. But what I can say for this book is it is easy to follow and the method of modeling that I have learned from it is very useful. If you can follow the tutorials patiently, you can gradually build a very good foundation of your modeling skill. ^-^.. I am looking forward for the next edition.

1)This book highlights some important issues in modeling & rigging that no other books bother to emphasis.

2)The accompanying CD contains very insightful scripts (that acutally works) - goodies other books only PRETEND to give.

3)It guides beginners and ease them through relatively advanced topics in character animation.

4)If you really need to achieve something in a hurry in Maya. Yes, this is the book to get.

For a book to be called game development this book sure is lacking on the game side of things.You create one big game at the end,but other than that there is really nothing else in there I would consider a game.That's why the book is getting 4 stars not 5.With that out of the way this book is very well written and the author explains things in great detail. There are alot of good nuggets of coding techniques in this book.

I had used Flash 4 for some time. In Flash 4, if you wanted to do a certain command, like go to a different scene you went to the point and click menu and selected that.But I felt that was rather lacking in what you could do, so I wanted to get the latest and greatest version of Flash. I went out and bought it, (MX 2004) and I soon found out, that there really wasn't a point and click menu, and you needed at least some knowledge in ActionScript. I looked around, and found this book. And I am glad I did. The book is exellent. It's really easy to follow, between the detailed explantions and the demo's on the cd. I found it really easy to understand everything, and it gives you a great way to start programming.

It comes with a demo of Flash MX 2004, but I highly recommend buying it (I got it at an educational discount). Both MX and this book were well worth the money.

There are few author's that take the beginner's (dummy) route to teaching programming to the masses and this book shines brightly in that department. From start to finish, it seems that the author knows what I want to do and shows me thoroughly how to do it properly with different ways to tackle it. I highly recommend this book to anyone that wants to take FLASH MX to sky high heights and not just leave this wonderful program to websites.

This is an enthusiastic book to read because once you open it and see how easy it is to follow you'll be excited to continue to read, and learn how to use flash mx. The author shows excellence in communicating the information to his readers. I am not fimilar with programming, but interested in programming and i was able to gain a lot of information that I was able to apply(which is the most important concept of the book). I definitely recommend this book to those who may want to enhance their knowledge or one who is just curious of the field.

I'm a business man looking for a programming book to spice up my computer knowledge & some fun, something different and exciting, I came across this book, in Barns & Noble, sitting on the shelve in the actionscript section. The book is very easy to understan, comes packed with not only that but the CD comes packed with cool samples and games and comes with Flash MX 2004!!! Defenietly I recommend it.

There was a time when artists bread and butter work was painting true to life pictures: portraits, battle scenes, ships, landscapes. With the advent of photography, art changed to other forms, some of which bore no recognizable appearance of anything known to anyone but the artist.

With the advent of digital photography and the necessary software to manipulate images, digital artists began to move in the way of the painters. Their digital images are formed by the manipulation of multiple images, of changes that can be made down to the bit level if desired.

This book explores digital art. While as of yet this is not well received by the conventional art community, it is a sign of coming times. Specifically in this book the same three specific images have been given to seventeen artists to use to illustrate what they might create. The procedures they followed to create new images coming from these three seed images are documented. The results are wildly different between the resulting pictures.

This is the forefront of digital art.

Joseph Nalven and JD Jarvis' Going Digital: The Practice And Vision Of Digital Artists is written by a cultural anthropologist who developed photography as a tool for working on ethnographic research, and an author who has long worked in TV production and graphic design: the two together offer a survey of the digital process as it applies to creating the art, from photos to finished products. 17 artists were asked to take three seed photos and use the images creatively in their own works of digital art: Going Digital takes these 17 efforts and blends them with discussions and examples of digital art from around the world, considering common challenges, presenting step-by-step processes from digital pioneer efforts, and creating a solid set of practical examples. A must for any aspiring digital artist.

Anything written about the practice of digital art today is doomed to be obsolete shortly. Very little is likely to survive even as being "quaint" in the way of Bill Gates's famous comment that 640 bytes were enough for anyone.
Since we have digital artists in the thousands, however, all eager to learn more technique, to make the most of all that's available, to see what each other is doing, we need resource material to serve them. "Going Digital" does this admirably in an original way. Seventeen artists each take the same three given photographic images and use up-to-the-minute tools to mold their own creations. The results are startlingly different. Most important, each artist has recorded his or her creative process in a sort of running diary, illustrated with dozens of images used or discarded en route to the final one.
The technology will more than likely change drastically as artists and computer scientists continue to interact. What will remain exciting and inspiring in Joe Nalven and JD Jarvis's book is the implicit discussions among editors and contributors about the meaning of art, the value of art, the place of artists, what changes and what abides. Both the many fine prints and the thoughtful questions raised fit into the history and practice of art, as always fascinating every one of us. Every question has more than one answer; rarely are these answers just yes and no. Although the discussion is implicit, the reader knows that he is in the hands of experienced teachers. The authors leave no doubt that their book goes past "now".
You'll want this book on your shelf or in your hand always. I wish that Amazon would let me give it a sixth star.

There is little that I can add to the previous excellent, detailed reviews. But I did want to add my two cents worth:

I received my "Going Digital" from Amazon a few days ago and read it cover to cover in two sittings - loved it! I especially enjoyed the participant's musings on the three seed photos. It was interesting that most all of them liked the image of the figure.

The resulting prints could not have been more different - a very interesting intellectual/artistic exercise indeed. It is a "must have" book for all digital artists - and will undoubtedly be a classic text book on the subject.

(...)

I find that having to create something with images not of your own choosing forces
you to stretch the limits - to step outside of your comfort zone. I have produced images that I NEVER would have done otherwise.

I have been working digitally less than two years, most of that time I have been in
an internet group with weekly challenges. I credit the "seed image" restriction with helping me grow and find my own voice in this digital world.

When I switched to digital everything was so new and unfamiliar. I have not been able to get into a comfortable rut with the ever-changing challenges. They have pushed me in directions I never would have chosen for myself- and that's a good thing!

When I finished the book I looked for a website that had the images available - I was dying to try my hand at it!

Buy the book, then try out the concept of "seed images" for yourself. It is a fantastic learning experience.

Oh wait... while I am here. Harald Johnson's other book "Mastering Digital Printing" (second edition) is another "must have" if you are serious about your digital art.

Carol
(...)

This book is a treasure trove of ideas for aspiring digital artists. Digital art has come of age, and Nalvin and Jarvis offer a comprehensive overview of the revolution that is transpiring before our very eyes. The book features an international group of digital artists working their magic on three simple images, while explaining their techniques and exposing their creative thought process at every step along the way. For the reader, each chapter provides a compelling intimate journey through the creative mind of a digital artist. My favorite was Greg Klamt, whose creativity is boundless. For me, this is digital art its at its very best. As Jarvis has stated in his digital manifesto, in the digital art world ".high cost will no longer signify superior work. Galleries and critics alike will soon have to realize that creativity, vision, diversity and craftsmanship have returned as the benchmarks of "value". Bravo!

This book has everything I need to know about computer networks. It's the best book I read about networking.

I read a review of the new Network+ exam from CompTIA, and this book was listed as being one you could use in studying for it since no books on the new exam were out yet.

Skeptically, I plunked down the money, read the book, and took the exam. I passed with 95%!

This is one of the best books I have read in preparation for the Networking Essentials Exam. The tear out booklet is amazing and was a great help the night before the exam. This book uses a lot of excellent illustrations and examples to explain concepts and ideas. The 'Key Concepts' section in each chapter focus on important points to remember for the exam. Using this book helped me pass this exam on first try. I highly recommend this book to anyone preparing for exam 70-073. This is the only book you will need to buy!

This book is fantastic and it covers in its pages what most books do in 600+ pages of fluff. The advantage is you don't get lost in the influx of information. I highlighted the book from front to back, then purchased the Transcender study engine - every question in that engine was answered in this book!

Unfortunately, I had to take this exam twice. So, be ware, do not depend on this book for the MCP exam. I am wondering about other people who previewed this book and said that they passed the exam using it???

I do not recommend this book for those who are planning to take the MCP exam. This book covers almost 50 % of the material of the exam. There are some poor parts in it which represent some objectives of the exam. These poor parts are: troubleshooting, performance enhancement, topologies, and protocols. From experience, I can tell you the following points are mentioned heavily in the two exams and were not slightly covered by this book which are:

*Troubleshooting: It does not tell you about the way to low-level troubleshoot a bus topology networks, which include measuring resistance in different parts of the network .

*Performance Enhancement: nothing about window size and packet size for TCP/IP protocol.

*Topologies: Nothing about mesh topologies.

*Protocols: Nothing about the TCP/IP suit and IPX/SPX suit. It does not mention which protocols are under these Protocols and to which layer do they belong to.

Besides, the sample test at the end of the book is silly and does not represent real MCP exams.

Comprehensive. A good resource to have in the collection of books.

Andre Van Staden - Senior Developer
Marco Giani - Group IT Back end Developer

This is a great book. I have recommended it to coworkers who also purchased the book and they were equally impressed. This helped me have a much greater understanding of both Access and SQL Server and how they work together.

I would highly recommend this book to anyone using Access with SQL Server. It is easy to understand and has plenty of useful code examples. I use this as a reference on a regular basis.

This answers a lot of programmer level questions about using MS-Access with SQL Server. It describes the limits and penalties when going the various routes. The book is quite clear in its descriptions. It would make a good addition to any Access programmer's collection.

I have been an Access developer since 1.1 (1993). I have bought many a book over the years. Some good, some bad. This book, however, is super! It is designed totally with the Access developer in mind. All of the questions that popped into my head seemed to be answered in practical terms chapter by chapter. The organization is terrific and the flow is second to none. The topics that are worth repeating are repeated while others are left for a one-time only view. The writing is easy to digest, powerful and very explanatory. The pictures are all also very helpful. You can tell the writers paid attention to every line they wrote. But they also inject a human kind of writing style which keeps things interesting throughout.

In addition to a thorough discussion on SQL Server security vs. Access security, data conversion, upsizing, etc., the book covers the differences among MDWs, MDEs, ADPs and ADEs beautifully and it addresses scenarios for when to use stored procedures, server functions, views, etc and with great attention to detail. The chapters ADO vs. DAO and on T-SQL are well written too. Later the book even goes into simplifying building multi-tier apps with Access as front end, VB-based COM+ components in the middle and of course, SQL Server sitting in the back. And just when you think the last chapter will be a letdown as many last chapters are, it wows you with an incredible amount of insight into how to optimize, backup and perform other settings in SQL Server.

If you are a serious Access developer like me, and are timid about moving full force into SQL Server, then this is the book for you! I recommend it highly!

I have a lot of SQL server books. Everything from SQL Server 2000 for Dummies up to SQL Server 2000 Stored Procedure Programming. And many times none of these books had what I needed. Then I would turn to this book. I was using VB.Net, so I figured this book wouldn't apply, but I was wrong. Even if you are not using Access, this book explains SQL Server the right way. Chipman and Baron offer simple but thorough explanations and samples of the things you actually need to know as a developer. They don't spend a lot of time on the things a SQL Server DBA might need to know that a coder would not.

Maybe their approach works so well for me because I came from an Access background, but I am willing to bet anyone coming straight from VB and needing to understand Transact SQL, effective stored procedures, funtions, and triggers would appreciate this book as well.

This book gives you all the goodies about Windows Server 2003, perfect view of what this new version has within, plus a lot more! This book was simple to read and understand, finished it in one weekend, and most of all, it's a great reference unlike some 2,000 Page Bibles...

It is clear, concise, and very well written. I get tired of reading tech books that are hundreds upon hundreds of pages long because they fill them with so much useless information and "fluff". That is not the case with this book. If you just want the plain and simple facts and useful information then this is the book you need.

This is an excellent book for those of us who have extensive experience with previous Windows releases, and need information dealing with just what's new and improved in Windows Server 2003. This book is well-written, well-organized, easy to read, and gives you everything you need, and nothing you don't.

I highly recommend this book to all experienced Windows Server administrators who need just the new info and just the facts, from authors who actually know what they're talking about.

Page 78: windows clients DO NOT require a GC server to find a domain controller.
Page 130: stub zones are NOT secondary zones with glue records. They contain read-only SOA, NS and "glue" A records and nothing else.

Returned my Mastering Windows Server 2003 (Minasi) book today and bought this one. MUCH better. Short, sweet, and to the point. Now I'm getting a handle on what I should care about in Windows 2003. This is great - I hope they keep up with this series. It's a time saver and I'm betting it will help with my MCSE upgrade exmas too.

The book weighs a ton and there's lots packed in it. Have not attempted to use the CD-ROM. Index helped me find specific answers to specific issues, since I don't know the program at all and had to hit the ground running. Have not been able to find answers to more esoteric matters, but the book has been invaluable for my quick-fix situations. Legal-specific and more useful on a daily basis than the "Dummies" book my boss bought. Thank you, Payne Consulting Group!!!

Any law firm that uses MS Word has been influenced by the work of Payne Consulting. Payne Consulting was in a conference that went into a committee that worked closely with MS to influence Word and to make it compatible to what law firms got used to with Word Perfect. Interestingly, Word finally has a feature that offers you the opportunity to recover documents if you had not saved it the day before.....wow.....why didn't they do that for corporations.

Well, if you are a Word Perfect user in a law firm today, you will want to open up new vistas by learning MS Word for Law Firms. I recruit in Legal, and this tool is useful to improving your skills and making a transition to a larger law firm possible.

real world advive for anyone interested in applications of word in a business setting

I found the book easy to follow with a lot of useful information in the form of tips and cautions. I purchased the book to prepare for the Word 2002 MOUS exam (and passed). I cannot recommend it highly enough.

As a forced convert from Word Perfect, I was looking for a resource that would allow me to do two things: (1) learn Microsoft Word; and (2) integrate it into my practice.

Ms. Payne's book helped me with the first task and made Word a much easier program for me to utilize.

I was somewhat disappointed, however, in the second aspect. I would like to automate my litigation documents to a greater extent, but I couldn't fully realize this goal. At the end of the day, I'd like to turn out better, more polished legal documents, but, I think there are some limitations in either my own understanding or the software that prevent me from being as effective as I'd like. At more than 700 pages, Ms. Payne's book certainly contains a good deal of information and suggestions as to how Word can be used in a law firm environment, but I found it to be most helpful as a Microsoft Word resource.

Great book for Oracle database professionals who want to deepen their understanding of the manifold factors that affect performance. I learned a ton of instantly useful information during my first pass through the book. I now keep this book within arm's reach as a reference, using it frequently to address tuning issues as they arise.

Hi,

This book is great for DBA and Developper alike. I would recommend it to anyone working with Oracle, even if you're not working to solve performance issues. With all those tips at hand never your application will suffer from poor programming.

Guillaume

In my opinion, this is the best Oracle press I've ever read in its quality. The book is well organized, has extensive tested examples and the author's strong experience apparantly added to the value of the book.
For those who want to be specialized in Oracle database tuning, this book is a must.
I wish all Oracle books would be in this level of quality.

I highly recommend this book as a handy reference to keep at your desk. It is full of handy tips and a great assessment for reviewing your own environnment.

I love reading this book. I typically read a few pages before bed. It's filled with lots of practical examples and suggestions. Very thorough explanations. Some of the examples could do with a little more explaining but overall it's still very useful.