Computers Books

I am an experienced developer but fairly new to VB.NET. This book is not for beginners but it is great for someone like myself who knows what they want to do and just wants some good examples and tips. It's a great reference book and a good alterative to Google. The English is clear and to the point. The book is a sturdy hardback and the pages are well laid out. It's easy to read afters hous of staring at a screen. To sum up, I'm glad that I brought it. It has saved me time and money and you can't ask for much more than that :-)

There is a lot of information in this book, covering a broad range of subjects. It is well laid out and easy to reference. The CD comes with the current version of the book as well as the author's previous book on VB6. Not really a beginner's book as there are more intermediate and advanced topics. I had not used .NET and hadn't touched VB6 in a couple of years. I needed a resource to help jump from rusty VB6 skills to .NET - this book did it perfectly. It is also filled with advanced topics that I am not currently using but now know where to go when the need arrives.

Fast service, great quality... What more can you ask for. I recommend this seller.

I bought this book few years. It is an excelent source of information and writers style is very clear. I just came back to see if Balena has book for C# 2005. Looks like I found something. I am going get that one. However, present book is quite good, check if there is a newer release you may want to get that one.

This was the first .NET book I purchased, and in many ways if I hadn't bought any others it would have been sufficient. It has thorough coverage of the .NET environment, with lucid code examples in VB.NET. I found the chapters on ADO.NET and the framework internals to be most useful to my job as an ASP.NET developer, but the coverage is deep enough that a person with very little programming experience could read this book and come away as a well-rounded .NET programmer. Even if you're writing in C#, as I am, the book is worth the money. I would also recommend Dino Esposito's Programming Microsoft ASP.NET for more depth if you're a web developer.

I am about 3/4 of the way through at this point. It is a fantastic book with a lot of good information. I would highly recommend it for anyone looking for a good methodology for network design. There is also a lot of good hints for things to keep in mind while designing the network.

This book is a very comprehensive reference source and working guide for 3G mobile networks. If you're only going to buy one book on the subject, this is it.

I purchased this book with the intent on gaining a further understanding of the network design process. I really didn't expect the book to give me as through an understanding of network design as what has turned out to be the case. Coming from the network support side this book has been a tremendous compliment to my support and logic in how traffic flows from A to B. I feel now that after having read the book which is an EASY READ that I have come away with enough knowledge to auctually design and implement a small to midsized company network. The authur does an outstanding job of presenting to the reader the many processes involved in through network design, network logic, and what exactly happens when your pc 1st boots and why it takes so long for the logon screen to appear "if this is the case on your network", and countless other topics. If you are just getting into network design or have been in the field and are a seasoned veteran I highly recommend that you add this book to your networking library.

Like the carpenter, the network designer does well to develop a plan before purchase. The title, Top-Down Network Design, is accurate because the author's key approach throughout the book is to consider what works best for the end user and meet the goals of a Request for Proposal. Priscilla Oppenheimer has presented a well structured textbook that covers every facet of networking in general with the intent of training the reader in the best practices of network design. The point of this book is to discourage going straight to product catalogs and picking out hardware when assigned a network project. Even if the customer is not given an RFP, the designer should present an overview of the project that includes the goals and how those goals will be measured.

The reader should have some basic knowledge of networking. However, this would make an excellent text book at a university or trade school since Oppenheimer covers all of the logical concepts and physical aspects of modern networking. The well read and experienced network engineer will find it a good review with a unique insight or tip sprinkled just often enough to make it worth the read. Except for the CCDP exam, the book is primarily a supplement to the student, but a must have reference for the consulting and design professional.

Oppenheimer gives well thought through, easy to read descriptions of technologies. For example, page 208 gives the most succinct explanation of how IPv6 works I have ever read. Another practical lesson is her definition of the "Heisenberg uncertainty principle" as "the act of observing something can alter what is observed." Consultants should be careful that their analysis doesn't become a problem in itself. Top-Down Network Design is a reference you will want to check yourself and those you hire.

Top-Down Network Design, Second Edition is both a new terrific book and still a terrific book. The original took a systems approach to designing a network which could provide the service the people paying for it expected, partly by getting them to clarify their expectations and needs. The new Second Edition does this, too, but it includes material relevant to the networks being implemented today, and they are very different networks than we saw even three or four years ago.

New technologies, such as VPNs, VoIP, IPv6 as well as v4, Gigabit Ethernet and 10GigE, etc. are covered as part of a networking solution, not just as cool and sexy technologies to be rolled out for that reason. Likewise, new business emphases like reliability, redundancy, resiliency (which are not the same thing), security, and even survivability are addressed. Not all new technologies will help solve these problems, and, more often than not, they aren't even necessary. Thoughtful planning is far more important, and working with the network as it is now, toward what it is desired to become, is how you can really solve these problems.

I think one of the greatest techniques you can learn from TDND, 2e is to characterize the flows of traffic on the network. Priscilla Oppenheimer gives several examples of developing such analyses in a variety of situations - campus networks, WANs, a design testing scenario, and so forth. The Appendix with workstation bootup traffic information is especially helpful - the only thing I would have liked to see that I didn't was a little more detail on the contents of the various packets involved, but it is an Appendix, and using a sniffer will let you see them for yourself.

I have both the original and the new Second Edition - and getting the new one is definitely worth it. Networking has changed, and this book will help you handle the new material.

This inspiring book is a must for all recruiters who understand the leverage power of online sourcing and networking.

As its subtitle suggests, The Virtual Handshake is all about interfacing with business and social contacts through the worldwide web. In my field (recruiting), the lines between business and social contacts blur since everyone I encounter might need either a new job or project, might know someone who does, or might be in a position to hire. Networking is not just about pressing flesh and passing business cards at a luncheon these days. There is a rapidly growing area of opportunity to meet people and make deals on the internet. However, please note that The Virtual Handshake does not merely expound the virtues of the internet or report results of deals closed and marriages made, the authors also make the technologies easy to understand and provide practical advice on how to use what's out there. Published in 2005, the book provides current information on various virtual options and their uses. The authors cover topic such as social software and services online; virtual clubs and associations; tips on managing the deluge of email; basics on blogging; effective use of email blasts without being perceived as a spammer; netiquette; privacy protection; and, of course, real-life examples of the use of the virtual medium. Easy to read and very useful, The Virtual Handshake is a primer for those of us who haven't been hip to the virtual world that's out there. It made me wonder if I've been living under a rock! The good news is it's not too late to learn, and this book will definitely help. I was so inspired by this book that I boldly went out there into the virtual world and set up my own blogsite!

This book delivers everything it promises. It is interesting from beginning to end and is obviously written by someone who is inspiring, articulate and experienced. It gives really good advice abot how to handle and manage one's growing familiarity with Internet capabilities and offers several good references for aspiring networkers. It even explains how to write a good resume.

The world is changing and so is business. The Internet, and various "Web 2.0" technologies, for lack of a better (or even good) name, are rapidly becoming an integral part of business and life.

The Virtual Handshake doesn't attempt to get you entirely up to date -- that's impossible, but up to speed -- that's far more valuable.

If you don't have any trusted colleagues you've never met in person or maybe not even talked to over the phone, you need this book. Even if you've spent a quarter of a century online like I have, you need this book. I learned a lot, and still refer to this book often. (If your secretary reads your email to you and you dictate answers, I suggest you retire or read this book ASAP.- You need help catching up).

After reading The Virtual Handshake, and I strongly suggest you do, you'll understand the basics, importance, and success guidelines of social software. You'll be up to speed in perhaps the most critical area of business change in our lifetime. The CURRENT wave of the Internet, and probably more important than the original commercialization and popularization of the Internet.

Hey, what's more interesting, the Big Bang Theory or How Life Came About?? This is the "How Life Came About" part and you'll learn about things like virtual communities and social networking, but far more importantly,- you'll know what to do. Actual steps you should take --- and plenty of case studies to help you understand their importance. Guidelines to harness the power of these new whateveryoucallthem.

Hint: be yourself, act responsibly, and remember you are the same person both online and offline and don't forget it!

There is a lot of valuable information in this book. Plan to read it, enjoy it, and then study it. And plan on concrete benefits.

It's a rehash of common sense. Do not waste your time reading this book.

I found this book to be extremely helpful in constructing an eCommerce site. It's a great book for an experienced VB developer to use to jump into developing an e-commerce site, even if you only go through the PayPal integration. It's also a great source of material on the construction of a shopping cart, and even if your "shopping cart" is only going to be used on a companie's intranet for product/supply request/issue, it's a great starting point. As a developer I can modify the business tier code to conform to my companies requirements and concentrate on the presentation layer.

This little book is chock-full of detailed explanations and examples of an e-commerce site built with ASP.net and an SQL database. It's simply the best and definitely most-used technical book on ASP.net I've picked up in the past 2 years! In addition to the detailed explanations, I especially like the lucid examples of creating and calling the SQL Stored Procedures. Learning by example seems to be the most effective way for this novice programmer to complete an e-commerce site, and this book has greatly reduced the amount of time it normally takes to scan through multiple sources of technical information when creating a complex application. Thanks to the authors, Christian Darie & Karli Watson, for providing a comprehensive resource!

I've used this book to construct my first e-commerce website, and I don't think I could have managed without it. The 3 tier design of the sample site is very well organised and easy to adapt to your own requirements. It also makes it simpler for a novice like me to understand how everything works. I found the second part of the book (dealing with the order pipeline and credit card transactions) harder to follow. However, when I contacted the authors about a problem I was having, I received a prompt and friendly reply that soon got me back on track. Thanks, Cristian and Karli!

This is an exeptionally well written book for the beginning webstore developer with

It walks you through a complete design of the side with the end result that you have a basic webstore that you could actually take operational. The only weakness in the credit processing section. It's written for a European credit card gateway. It would be nice if one of the more popular US gateways (e.g. authorize.net) was also included.

I also sent a couple of questions to the author and he was responded very quickly ... obviously he's interested in making sure everyone reading the book is successful. 5 stars for that alone.

This is primarily a book about constructing an ASP.NET web site using stored procedures, and less a book about e-commerce. There are a few sections, mostly at the end, which are specific to e-commerce. These include the order processing pipeline chapter and the credit card transactions chapter.

This is not to say the book is bad. It's very well written and the code is described step-by-step in detail. There could have been more emphasis on architecture, and a little more on e-commerce. I would also like to see some emphasis on the sticky legal issues like customer data management, password security, transaction security, and how and when to migrate the data off of the machines on the open Internet and back into safe storage on the Intranet.

I've never read a technical book by someone with such an enormous ego.

This cover and explain the details about Network

"Interconnections 2nd Edition - Bridges, Routers Switches and Internetworking Protocols" by Radia Perlman is simply a magnificent book. This book is a one-stop introduction to both Layer 2 and Layer 3 of the OSI model. This book will not teach you how to configure equipment - but what this book will teach you is how different protocols interact with each other. Most books only focus on either layer 2 or layer 3, but this is the one book that discusses both layers better than most books discuss each layer individually!

Some typos that I noticed in the 2nd edition:

Page 186 - concerning the 4th bullet - a router would fragment a 1,200 byte packet to a 1,000 byte packet and a 200 byte packet - not a 1,000 byte packet and 2,000 byte packet.

Page 209 - The IPv6 address that starts as FEA0::/10 should really be FEC0::/10

It is obvious when reading this book that Perlman is writing about a subject that she both has mastered and cares deeply about. She holds over 50 patents and has earned her Ph.D. from M.I.T. Simply a great book.

I give this book 5 pings out of 5:
!!!!!

This book is a fantastic voyage through the world of networking. For newbies, it presents complex ideas in an easy-to-understand and entertaining way, keeping you away from an alphabet soup of acronyms. But, it also appeals to experts as well, with its insider's view of the design of various network protocols. Even with many years of networking under my belt, I found myself reading this book constantly saying, "So, that's why they did it that way!" The wealth of information in this book should not be overlooked. The writing style is also crisp, clear, and highly engaging.

Perlman does a fantastic job of writing about a topic she's obviously passionate about. Her ability to convey complex networking topics simply makes this book an excellent introduction to the subject, a great guide for people who don't need to be experts (i.e. marketing folks), and a technical text book. This book is both incredibly informative and entertaining, spiced with some of her own views, annecdotes, and history of networking. A great read, can you believe I would say that about a networking text?

I know nothing about computers, but enjoy using software. This helped a bit for my lack of technical knowledge. There's probably a lot more info. in the book that I just can't bother getting around to.

I noticed that the people who really like seem to be hardcore Mac users (i.e. 'I've used Macs for 10 years', etc. ). The people who just want to use a computer didn't like it much. So, decide which kind of person you are before you buy.

Although I have since switched to Mac OS X (aka OS 10), I actually used this book first. It was an invaluable tool in easing my transition from Windows user to Macintosh user. I would recommend all Mac users switch to OS X as soon as possible since it's a much more stable and reliable version, but if you have an older Macintosh then OS 9 is a fine Operating System.

If you need help learning how to operate your Macintosh with OS 9 (OS = operating system - the graphic user interface that you see when you turn the Mac on) then you can do no better than this book.

If you're completely new to computers you'll find this book immensely helpful as it holds your hand in the first few chapters and explains how to use the GUI (graphic user interface), the mouse, the keyboard and so on.

If you're new to Macs it will also serve as a primer to get you up to speed very quickly on how to use the Macintosh and learn the Mac way of doing things.

If you're someone who knows how to use Macs this book will also help in the later chapters by showing you how to become a "Power User". It will help increase your productivity, teach you all the great short-cuts and keyboard combinations and so on.

All the books in the "Missing Manual" series are very easy to read, with detailed step by step instructions along with a fantastic index for simple cross-reference and nice pictures to further simplify the process of learning.

Be sure to check out "Mac OS X: The Missing Manual" if you're looking for the best and easiest to read book on Apple's fantastic new Operating System.

Unfortunately I'm limited to two thumbs because otherwise I'd be tempted to give this twenty thumbs way up!

Of the many computer books in my posession, Pogue is the best by far! Everything from Macs for Dummies, Mac Secrets and now the Missing Manual series. If the answers are not there Pogue is on the web and will answer questions as well as take suggestions for future reference. In my humble opinion, if it's Mac: Pogue's The Man! This is after several years including a newspaper job with many macs and variety of probs. Also, He return emailed me to suggest NOT to buy a current edition because a newer, more suited to my needs, would be out in a few months. I also bought and love OSX. Thank you David Pogue.

I preferred this book over "Mac OS 9 for Dummies", because it has more "meat" in it, and is generally more readable. I found it an excellent book for someone who is essentially computer literate, but wishes to move from a PC to a Mac. The front of the book touts that OS 9.1 is also covered in this volume, but alas only a few dozen words, which seem to have been slipped in at the last moment. The Dummies book does one thing better, which is how to select which Extensions to disable so that your Mac isn't clogged up with bits it doesn't need. My advice would be to buy the Missing Manual book if you have, say, a PC at work, but want to buy a Mac for use at home. It will help you move from one to the other easily and in an entertaining fashion.

OO design and analysis is so very gray. No book can cover every aspect because the possibilities are endless. Everyone's application and environment is different which causes each and every one of us to approach our design differently and value different affects of our coding practices. By far this is the best book I have read that simply lays out OO rules-of-thumb and then explains why each is beneficial and when they might contradict other rules-of-thumb. The book encourages the reader to be reasonable and practical in your application of OO best practices.

I strongly recommend that every development team read this book and discuss it amongst themselves.

Ok, I had to look up heuristics in the dictionary before buying this. But other than that I found this to be one of only a handful I've read that tells you how to look at OOD work you've done and decide if it is good (and how to improve it). Particularly good was the discussion of cases where design goals conflict and how to resolve the conflict.

I have been studying the object oriented methodology for some time now. I felt that I had a good understanding of what OOP was all about. I have studied OOA/D and design patterns from numerous sources. All of my sense for OOA/D knowledge changed completely when I read this book. This book really showed me that I was stuck somewhere in the middle of the paradigm shift between action oriented programming (aka procedural programming) and object oriented programming. After reading this, I feel like my knowledge in OOA/D has truly advanced to the next level.

Are you the type of person that knows what OOP is? I mean, if you've studied up on OOP then you are probably aware of what an abstract class is. You know what interfaces, inheritance, polymorphism, information hiding (...etc) are. You may have a sense in when you should use inheritance and when you should use containment. You probably follow certain OOP practices like keeping all of your variables private, hiding secrets from other objects (information hiding). This may all make sense to you but are you also the type of person that just never feels comfortable about your designs? Do you look at your classes and just get a sense that something doesn't seem right, yet you just can't figure out what it is even if your software system is running fine? I am willing to wager that you are in the middle of a paradigm shift. You are probably taking the route that a lot of developers take when they shift from thinking in a procedural fashion (action-oriented design) into object oriented design. There is nothing wrong with this, but if you're like a lot of developers you will have a long hard journey utilizing a lot of experience before you really make that shift. This book is an essential tool that will help you make that shift a LOT faster. After reading this book you will see why you felt your designs were't quite right.

One of the first topics that really hit home for me was when the author Arthur Riel talks about God classes in chapter 3. God classes are classes that have too much implementation in them. Most of the complexity of a piece of software resides in these classes. They are the all-knowing classes that delegate messages between the much smaller, less complex classes. Signs of God classes are classes that have words in their name such as "Manager" or "System" in them. This one hit home because there are numerous classes in the software i'm working on now with the name Manager in them. For example one of our classes is called the "BiDirectional_Dataflow_Manager". This is definitely a God class through and through. While I was reading about the disadvantages of these types of classes I couldn't help but agree with everything Arthur was saying. I began to see the light already and I was just on chapter 3. There are 59 other Heuristics, all equally important in this book.

Most books that teach OOA/D seem to really only teach the definition of OOA/D and perhaps clue you in to the whole idea. You learn the terminology well and you see a few examples (I'm sure you've seen an animal hierarchy a time or two), but you don't really gain a solid understanding in how you actually think in objects. This book will bridge that gap. This is the best book i've read by far on OOA/D. This book will apply to you no matter what your skill level is in OOA/D, unless you're a complete beginner then you might find yourself a little bit lost. If you are brand new to OOA/D then you should probably read a short book on OOP, just to gain the basic concepts first. "Object Oriented Thought Process" might be a good start as it's short and sweet, then you should move on to this book. If you are advanced then you may know a lot of this information, but this book will probably help tweak your OOA/D skills; helping you become an even more solid developer. But for you guys and gals out there that know what OOP is and read a few books on it, but still don't feel quite right about your designs, this book is essential. You guys out there are the sweet spot for a book like this. That's how I was. Now I feel so much better, I feel like i've gained more knowledge in OOA/D with this book then all other books on OOA/D and OOP that i've read combined - and then some.

Arthur Riel is a very talented programmer and author. He is able to communicate ideas to you that are sure to hit home, as if he's right there with you and understands your problems in OOA/D. This book is densly packed. Not including the bibliography and index this book is a mere 367 pages. Even more, if you don't include the example code at the end of the book (all C++ code) this book is only 243 pages. The real meat of this book is in the first 9 chapters (where he talks about all of the heuristics), which totals 182 pages. After that he talks about topics such as handling memory leaks and such. Most of the dim lights will shine brightly after a mere 182 pages! This may sound too good to be true, but as I said earlier Arthur is VERY talented in communicating his ideas. You just have to read this book very carefully, don't skim! Because it's so dense, it may take a couple of passes before you really get the idea but once you understand it you will surely belt out a resounding "AH HA!". This book is 10 years old at the time of this review, but the information inside is far from being outdated.

To conclude this lengthy review (sorry about that) I would like to say that I give this book my highest recommendation. In fact, this may be the best book on software development that i've ever read! This book has influenced my software development more then any other book i've read and that's a fact. This is truly a rare gem. The only downside (not this books fault) is that it's become a bit harder to work on the software that i'm currently working with because I now see where all of the pitfalls are. My co-workers think i'm just being anal about design now, but you don't have to be like them. Step up, become the best software developer that you can be. Just read this book and you will take a giant leap forward in your OOA/D understanding, especially if you're stuck in a paradigm shift like I was. Thank you very much Arthur!

I have plenty of books on patterns, but I want to get more information on the basics of OOP and why the patterns are effective instead of "this is pattern X, and this what it does." This is a very complicated subject, which I have no doubt that most programmers on the planet have very little understanding of. We mostly write crummy code that "works", and most of the time that's good enough.

I was uncertain about getting this book because of how old it was, but after reading most of it, I'm happy I got it. Although complex, it is written in an understandable manner with useful diagrams. I wasn't as interested in the "one-liner" heuristics as I was the detailed explanations of the problems caused by particular design mistakes and the other examples and pitfalls presented.

Regrettably, I disagree with the other reviewers here who seem to have liked this book. I didn't. Not that it's terrible: I found myself in agreement with most if not all of the rules of thumb the author talks about; the problem is more that this book is not well done.

First, this is a textbook; as such it is aimed at a student, that is someone who doesn't know the material yet and tries to learn. But for a tutorial this text overwordy and imprecise, with a generous quantity of confusing, misleading metaphors. If you happen to know what the author is trying to say, then you sorta get it -- I mean, you get it 'cause you already know it -- but a newcomer will be confused.

Sometimes the author doesn't seem to know why a particular rule is good, so he goes something like this: rule such-and-such is good because most software engineers would agree that it's good. I doubt the author conducted a statistically valid survey -- but forget that, suppose most software engineers do in fact agree: so what? All the author has now is a nice and juicy ad populum. But he, obviously, isn't even aware that something's wrong -- and that may be one of the problems with this book: the author may not be experienced enough to write books of this sort. He may be a competent practitioner, but this is not the same as teacher.

He tries to compensate via an over-abstract and smart-sounding terminology (one of the reviewers below jokingly complains that he needed to look up the word "heuristics": that is a telling comment, and it is valid. I, too, noticed that the author takes delight in using a dozen hifalutin words where one simple word would do (and result in a clearer text).

Riel also likes to belabour commonplace excessively ("data should be hidden inside objects"; "Objects should not depend on their users", blah-blah, brush teeth daily, apple a day etc.), anything to make the book thicker -- which brings me to its second defect, less important and quite a common one today: the book is blatantly padded. Out of about 400 pages only about 200 have readable text; the rest is mostly a source code printout (this code could have been supplied on an attached disk or put on the net somewhere). There's also a few pages with a concise restatement of the author's rules, which could have been printed on the cover insides (like in the Stevens network books) or supplied as a pullout; otherwise this list is hard to find and serves no purpose.

To summarize: were it better written, Heuristics could be useful for a newbie, but it's not and so it isn't. A more experienced reader, despite being annoyed, will understand it -- but only because he already knows the stuff himself and will be recognizing rather than learning. YMMV, but in my opinion this tome isn't worth reading time for any reader, new or experienced. I'm sending it back.

I have the book for almost two years and use it
quite often. Devraj explains not only database, but the whole system. It is crucial for any good DBA to understands systems and software architecture. This book explains it all. Great explanation about mirroring. The best book on Oracle Database ever.

This is an excellent book and I learned a lot. The only problem of this book is the papers continue drop down after I read it for three month. I have to say the writer and knowledge are excellent, but manufacture bound quality of this book is low.

I haven't been a DBA for very long and although this book has everything in it explained very well, I'm not sure that I would recommend it for beginners. Beginners need more detail, which understandbly you can't fit into any one book. But this is definetely excellent as reference material to start you off in the right direction. I wouldn't dare do standby without it!

While this comprehensive book is a definitive and complete reference for Oracle DBAs who need to support mission-critical databases, it is also a key reference for developing a comprehensive high-availability posture in Oracle-centric enterprises.

This book focuses on making Oracle highly available and resilient, but also touches on related aspects, such as hardware, operating systems and networks. What I particularly liked is the way the book begins, with an exceptionally well-written chapter on identifying your uptime requirements. All of the material here applies to availability and reliability of enterprise-wide systems, not just Oracle. In fact, Parts I and II of this book should be read by anyone who is responsible for implementing and managing a 24x7 enterprise regardless of whether they are a DBA because the information in the first two parts of this eight-part book will have the whole team (SAs, DBAs, network analysts and service delivery/support staff) using a common framework.

The remaining six parts span chapters 7 through 20 and are specific to Oracle. There is an overwhelming amount of information here. What makes getting through these chapters so hard is the fact that nearly every page has some important tip, fact or technique. The sheer number of these, all of which are important, will consume two or three highlighters before you get to the end of the book

Overall, this book is essential for Oracle DBAs, and deserves a place in the library of every architect and operations manager in large 24x7 enterprises that use Oracle .

This is the only book I've read that refers to multiplexing and mirring the control file in words you can actually understand! I now understand the impact of both techniques, and I can make a quick decision on how best to use the features. You'll want this book after being exposed to all the other material on Oracle, because then you can appreciate the subject matter. There tends to be a "confusion zone" surrounding Oracle learning because the Oracle database tends to be so over-engineered in some areas. I'm sure the information in this book will apply to version 9i as well. Good job on what I've read so far.

This guide is the definitive guide to advantage. No where else on the planet can you get the information detailed in this book.
If you use advantage, you must have this book!

I was a beginner at database usage, but I was able to pick up the nuances of ADS through the use of this book. It is my main source of reference for questions concerning ADS, and has helped solve many of my problems. ADS is a great resource, and this book is the ultimate companion.

Our company (Hudson Medical Systems) has been using the Advantage Database Server in our medical transcription and dictation products for over 3 years now and we could not be more satisfied with its ease-of-use, performance, and cost. I was pleased to see a new book devoted to this remarkable product that explains the unique features of ADS in such a logical and straight-forward manner. We especially liked the dicussion of the new features in version 7.0 that we are interested in. I would recommend this book to any database developer, regardless of their familiarity with ADS, as a great resource when developing applications.

We have been making Point Of Sale Applications since the DOS days and have been through several databases over the time. Advantage Database Server has performed far beyond than we ever expected from any Database Server Software. Programming in Delphi, we found the Advantage Database Server to be the most flexible and powerful Database Server and still reasonable priced. I wish we had have this book from the start. We have used Advantage Database Server for over three years and we have learned a lot by reading this book. You, definetly, need this book if you are looking for a new database server or you are already using Advantage Database Server. You don't want to miss out on this book!!!

Whether you're upgrading a BDE app to a client server database or developing a new single-user or scaleable multi-user app, Advantage Database should be at the top of your list of databases to consider. Native Delphi VCL components, ISAM file formats, free local server, easy installation and maintenance-free design make designing and deploying ADS apps a snap.

Now with "Advantage Database Server: The Official Guide", Cary Jensen and Loy Anderson have made life even easier. Although the Advantage help file documentation makes an excellent reference, it's no substitute for Jensen and Anderson's step-by-step guide to creating an Advantage database, connecting your app to it and deploying your end product.

If you've attended one of Cary Jensen's excellent Advantage Workshop seminars you'll recognize that this intuitive, and easy to read book is based on his well developed course book. If you haven't yet had the benefit of Cary Jensen's Advantage Workshop, you probably won't need it after reading "Advantage Database Server: The Official Guide"!

Whether you're an Advantage expert or rookie this book's a keeper as both an introduction and a reference. If you're looking for a low cost, maintenance free, high performance, scaleable database that you can learn to use and deploy in a day, this book and the included companion CD contain everything you need to get started.

This C++ core language book is so often used that I thought it may deserve a review.

I own 3 books about C++ and this one became the reference. Only 200 pages (compared to the 1000 pages of another one :) but every useful feature is well explained. Authors payed careful attention in order to prevent the reader to fall in common traps. Lots of examples, always accompanied with relevant comments.

C++ in a core language really answers the questions the beginners have in mind. Concise, pragmatic, the authors are not showing off, they simply remember they were beginners one day and their explanations are exactly what one can expect. Well, I'm so happy about this book (this morning again, I was looking for a reminder about "virtual" functions or a detail about the copy constructor and all my worries were answered with no ambiguity at all) I went straight to to Amazon for a review :)

This book is relatively short, but many people might see this as a good thing, since it is really intended to transition C programmers to the basics ("core") of C++. I believe it does a decent job of this, although there are some topics (such as const) that I think it should cover but, surprisingly, does not. I liked the comparisons between polymorphism in C and C++, and the explanation of virtual functions. The examples are pretty good. There is some great humor in the book, and some parts actually made me laugh out loud. Overall, I would suggest the book to any C programmer who wants to transition to C++. Get this as your first such transitional book, then once you understand the basics, move on to a more comprehensive intermediate level book.

C++: The Core Language is a well written book and a pleasure to read. It appears that that authors made an extra effort to remove unneeded verbiage. I appreciate this because I have so much to read.

The bread and butter OOD concepts of abstraction and polymorphism are well covered. The chapter on templates covers this difficult subject well, however, I would have liked to have seen a little more on template functions.

I came from a Kernighan and Ritche C background (the "C' bible), and this seemed to pick up right where they left off. You could call this book K&R part II, and it is also about the same size. If you want a complete C++ bookshelf, I would also recommend buying (in this order) Effective C++ by Scott Meyers, The C++ Standard Library by Nicolai Josuttis, and C++ in a Nutshell by Ray Lischer.

-ND
www.NicholasDiToro.com

This is an excellent book for C programmers coming to C++ for the first time. I found the writing style and organisation of topics to be very good. The authors describe key object-based and object-oriented concepts first using familiar C constructions and then extend those ideas into the C++ domain. The ease of transitioning from C structs to C++ classes was very good, as was the discussion of subtle points like the copy constructor. Almost all major C++ concepts are described, including inheritence, virtual functions, and even templates.

My only negative criticism is that the authors leave out some important C++ functionality from their view of the C++ "core." They only mention in passing the use of const, considered by many to be vital to good C++ design. Also, since this book was published in 1995, it does not discuss the C++ standard library, which was finalised in 1997. It is therefore missing a discussion of the very useful 'string' class, among many others. Readers should defininitely follow up on these topics.

Regardless of this missing information, this book will give C programmers a solid foundation for using C++.

As an undergrad and passionate dbl major, having read many books in C and C++, this book quickly became my friend. It's a good read for those breaking out of C to C++. This book helped me cope with the shock experienced while I was trying to learn ADTs, BSTs, splay trees, skip lists, multiway tries and extendable hashing in the high level programming courses where if you asked questions you'd look dumb. The information in this book made me feel contiguously good while sitting in class. It also served as another perspective and filled in the gaps that the professor and school text left out. Also, pick up Robert Sedgewick's Algorithms in C++ 3rd Edition, which is also a splendid read.

Enjoy helping computers understand people!

late-