Microsoft Access Developer's Guide to SQL Server Revised and Expanded of " Arom ed. Edition

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 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 is a good book, but many things have changed in SQL and Access. I found more recent books to be more helpful.

I bought two similar books at the same time, only this book tells me the detail I really want to know .If you are a user who upsized your Access database to SQL Server, and had problems or questions about your database, this is the book you should read.

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.

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.

I've been an Access developer for the past 10 years. Now our company is finally migrating our data over to a SQL 2000 database. This book is an excellent resource for those transitioning from Access to SQL. The information is well thought out, laid out in an easy to use format, supplies good examples, and has a tremendous amount of useful information.

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.

Having developed Access applications for a number of years, I was asked to create a system utlising SQL Server as the backend with a windows interface for the client. I knew Access was able to communicate with SQL server, but how that was achieved was unfamilar territory. The book guided me through the intracacies of the subject revealing the different mindset that was necessary to achieve the desired result. Loads of useful code examples, all downloadable from the web. One comment, the Index at the back wasn't comprehensive enough. However I read the book from cover to cover so was able to locate all the subjects I needed. Not recommended for those who are unfamilar with Access or database terminology.

Just what you'd expect when ordering, what more can you say other than it does pretty much what it says on the tin...what more you could ask for

A really good book for Access to SQL Server - a little dated now as all references are to SQLServer 2000 (note: SQL Server 2008 has debug for T-SQL which speeds up the learning process).I'm glad I bought it - apart from the binding being really poor so all the pages gradually come loose.I'm sure book binding was sorted sometime in the middle ages - another lost art!

Everything I needed to complete the job -and improve my skills. The platform(s) referenced are a bit old, but the content of the book and the ideas pushed still stands.

This book was certainly great when it was first published. Unfortunately, it is outdated. Still I learned quite some interesting techniques. It would be great to have an adapted updated version of this book.