Most Helpful Customer Reviews
45 of 45 people found the following review helpful:
5.0 out of 5 stars
If Access was dead, Mary and Andy sure brought it new life!, December 20, 2000
This review is from: Microsoft Access Developer's Guide to SQL Server (Paperback)
They pulled no punches: from the very beginning of the introduction to this book, Mary and Andy hit the very first point that every Access developer has to deal with -- Access is dead, Access is a toy, etc. etc. Of course, 800 pages later they have proven that all the people who thought this were not very bright (or at least did not know much about Access!). Especially cool are the huge chapters on views, stored procedures, and Access reports. I usually am pretty proud of the fact that I do not ever learn very many new things from books. But Mary and Andy ruined that one pleasure for me because I learned things that I did not know about, even when I was working on the Access team, in the source code! I mentioned the chapter on stored procedures, but I wanted to emphasize that these 52 pages are one of the most impressive intros to using them that I have come across. It is at the perfect level for an experienced Access developer who does not want to have feel dumb for "starting over" in SQL Server. In fact, the whole book is designed that way: you can leverage all your existing knowledge to help you learn about another, more powerful platform -- and the long term direction of Access itself. This book is a must have for anyone who wants to make that jump from Access to SQL Server: whether you are using MDBs or ADPs, traditional forms or DAPs, stored procs/SQL or ADO recordsets, if you are doing anything that go between Access and SQL Server then THIS is the book that will take you there.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
43 of 43 people found the following review helpful:
5.0 out of 5 stars
Other Books are "Streets", this one is a "Highway", September 10, 2001
This review is from: Microsoft Access Developer's Guide to SQL Server (Paperback)
In the last 18 months I have spent time and money reading a dozen of books in order to acquire the necessary knowledge to migrate from Access to VB/SQL Server. I've tried the enclosed code and learnt many things. However, until three days ago I didn't know "how" and "when" migration would happen. I've read this book in 3 days and only now I know I will start tomorrow! In every book I read I found something helpful, but this one is simply a highway leading you to the right place. Chapter 11 is impressive. Only after reading those ninety pages I can say that I know the difference between MDBs and ADPs. I mean when and how to use each of them, which problems I'll encounter choosing MDB or ADP, which limitations, etc. When and how to use DAO, ADO or ODBC, how to mix them in the same application using stored procedures at the server level. Chapter 14 on n-tier apps is just a bible to me. This is not a reference on SQL Server or Access, but if you want to know how to migrate from Access to SQL Server, what are the differences that you, as a programmer, must know, when and how to use remote data or local data, how to build a 3-tier app, you can't miss it. I don't know if I'll switch to VB or I'll continue using Access as a front-end. What I know is that also if I decide to switch to VB I will keep this book on my desk all the time. Thanks to both for this wonderful job.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
20 of 20 people found the following review helpful:
5.0 out of 5 stars
Very good book, June 17, 2001
This review is from: Microsoft Access Developer's Guide to SQL Server (Paperback)
In October 2000 I had to create a reliable Access / SQL-Server project but I did not find any useful documentation. A few months later I found this book and gladly it shows the same techniques I developed. If anyone tells you to migrate Access tables to SQL-Server read this book first !!! One remark though: the authors suggest to use Stored Procedures wherever you can. Using Views for Select queries is faster and you can put the SQL-statements in your VBA-code.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
|