|Title||:||Hitchhiker's Guide to Visual Basic and SQL Server, 6th Edition by William R Vaughn (1998-10-01)|
|Publisher||:||Microsoft Press 1773|
|Number of Pages||:||383 Pages|
|File Size||:||962 KB|
|Status||:||Available For Download|
|Last checked||:||21 Minutes ago!|
Hitchhiker's Guide to Visual Basic and SQL Server, 6th Edition by William R Vaughn (1998-10-01) Reviews
This SEEMS to be one of the better of the innumerable VB books out there, one which overviews medium to advanced database access concepts especially with relevance to SQL Server. I knew I was in good hands when I installed the test biblio database and saw it was not made up of garbage, but instead consisted of tables with real workable worldly data in it. A bunch of other books out there deal with ADO, RDO concepts but not with just the right level of detail that this book does. Explanations are "bite size", crisp, and to the point and the "content thread" overall progresses in a rationally hierarchical manner so the reader builds on, and is eventually equipped with sound methodology to implement the tools of SQL SERVER data access. A good measure of this book is in the discussion of RDO parameter queries to stored procedures, which the author scrupulously details with respect to output and input "placeholder" parameters, something that was rather sloppily described in the WAITE "how to" database access book. (But then it only gave 50 pages to RDO, and 77 to ADO!) I am tired of endless books that claim to discuss a topic in detail but which really give you 2-3 meager chapters on it with another 11 "kitchen sink" discombobulated chapters i.e. Crystal Reports thrown in. Attention all publishers out there: If I want to know topic, I need the detail on that topic and that alone, please - no more "salad bar" anthologies! This book mercifully, keeps to the straight and narrow on ADO,DAO,RDO with historical precedents thrown in which I always appreciate. I also appreciate that the book does not redundantly list source code that is already on disk! This to me is one of the dumbest things publishers do, why do I need endless pages of source code in the book AS WELL as on disk??? Also appreciated was the tone of the book, which treats the reader professionally, intelligently and never in a patronizing manner as opposed to the "idiot's guide to....." (I HATE THOSE BOOKS!) All in all, the book is an excellent reference/guide to what it professes. I would have liked a bit of overview on say, the normalization process because I feel these topics are of immense value. (But then the book does not really claim to explain database modelling anyway.) All in all, the 900 pages on everything in this book is really well presented and will be very useful to developers creating workable database access programs in a real world scenario. Good stuff.
I cannot give this book five stars although it contains lots of valuable information some of which it is hardly possible to find elsewhere. Unfortunately, sometimes this information is scattered over a few chapters, and it is not sufficient to go to one single section in order to study one particular topic; sections/headings are not very well organised. I realise that HG is not a reference manual, but even if you read it from cover to cover (what I have done), you need to make a lot of efforts to put numerous pieces of the picture together. Another thing that I dislike about HG is that you have to know (and remember) basic stuff like syntax or to have a reference manual on your desk when you are reading HG. Just this creates an impression that the book does not suit beginners. In fact, it does! Just make sure to check out what is written in the reference manuals before reading a chapter or a section in HG. If you are a beginner, you can skip Ch. 4-8. If your are interested in DAO and RDO (with VB and SQL Server), all you need is MS manuals and HG; if you want to learn ADO (with VB and SQL Server), all you need is D.Sussman's ADO 2.0/2.1 Programmer's Reference from Wrox and HG (BTW, guys who admire the Wrox' book, you can find something new for you in HG!). The coverage of the Visual Database Tools in HG is excellent.So, the book is not perfect, but it is extremely useful, and I don't think that there is anything better about VB programming for SQL Server on the market.
The terrible thing about on-line reviews is that often times very happy readers don't write them. So I thought, it was about time I did.I've purchased that last three editions of Bill's book. Why? Because simply put, 'It is the best book on Microsoft data access technologies available for VB developers'. It focuses on one back-end, SQL Server, and the multitude of API's available.The irreverent tone which some people find 'offensive', IMHO, simply adds character to an industry which at times really needs it. The code samples which I retrieved from the CD, always make getting up to speed quick and easy. Having heard Bill speak at VBITS and spoken to him, he is always trying to provide VB developers with the best information.The seven detailed chapters on ADO are well worth your money even if you have the previous editions; not to mention the details on the T-SQL debugger in its own chapter. Also, even if this is your first purchase, the previous edition's chapters on VBSQL and ODBC are still included on the CD! For many of us, ODBC still has a place in our development lives.The code Bill gives you is designed to focus on data access. If you need help with VB skills or UI design look elsewhere. But if you want down and dirty code focused on how to get to SQL Server, buy this book.
I bought the fourth edition (several years ago) and never really used it. The DAO model was explained much better (and quicker) in "The Jet Developers Guide". However I find myself upgrading to ADO with an accelerated deadline staring me in the face so I go to "the source" for VB and SQL Server - the Sixth Edition. The writing is wordy. The jokes come a little too often. The detail is detailed. It took me two days to pull out code that I should have been able to get (and understand) in half a day. I would recommend that a working example be given and then explained in depth rather than building the entire access method from scratch. If you are familiar with data access you would go back for the details on an "as needed" basis. I noticed that someone mentioned errors in the example code. There were errors in the fourth edition and when the fifth edition came out the first thing that was examined was the errors - they were still there. Perhaps it is time for a little housekeeping with the material.