By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,155 Members | 2,518 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,155 IT Pros & Developers. It's quick & easy.

Books for Access fe to SQL Server be

P: n/a
A number of people design systems with an Access front-end linked to a
SQL Server backend. Can anyone please recommend any good books which
set out how to do this?

I am interested to learn the techniques of building a .mdb (not .adp)
front for a SQL Server backend.

I have the book by Mary Chipman and Andy Baron: Microsoft Access
Developer's Guide to SQL Server. Although this is well written and
helpful, it spends much time showing how to upsize an Access backend to
SQL Server. I have tried this but still encounter problems. It
appears that simple Access databases can be upsized but complicated
ones need to have their front end redesigned. I am interested to find
out what is good design in this situation.

I want to find out how to start from scratch, desiging the Access front
end with the specific intention of using SQL Server backend.

Should forms be bound, with Recordsets? or should they be unbound? If
so, how best to get some data and to store any changes?

Should lists and combo boxes have RowSources or should this be handled
by code?

Jim

Nov 26 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a

Jim Devenish wrote:
A number of people design systems with an Access front-end linked to a
SQL Server backend. Can anyone please recommend any good books which
set out how to do this?

I am interested to learn the techniques of building a .mdb (not .adp)
front for a SQL Server backend.

I have the book by Mary Chipman and Andy Baron: Microsoft Access
Developer's Guide to SQL Server. Although this is well written and
helpful, it spends much time showing how to upsize an Access backend to
SQL Server. I have tried this but still encounter problems. It
appears that simple Access databases can be upsized but complicated
ones need to have their front end redesigned. I am interested to find
out what is good design in this situation.

I want to find out how to start from scratch, desiging the Access front
end with the specific intention of using SQL Server backend.

Should forms be bound, with Recordsets? or should they be unbound? If
so, how best to get some data and to store any changes?

Should lists and combo boxes have RowSources or should this be handled
by code?

Jim
Nov 30 '06 #2

P: n/a
I need to upsize a database to SQL server and was looking for a good
book to help me redesign my front-end. I just picked up a book that
looks very promising : "Building Microsoft Access Applications" by John
L. Viescas. It has a 50+ page chapter on designing client/server
applications. The CD has 4 sample databases on it. It is an advanced
book that looks to have much useful information.

Nov 30 '06 #3

P: n/a

Mary wrote:
I need to upsize a database to SQL server and was looking for a good
book to help me redesign my front-end. I just picked up a book that
looks very promising : "Building Microsoft Access Applications" by John
L. Viescas. It has a 50+ page chapter on designing client/server
applications. The CD has 4 sample databases on it. It is an advanced
book that looks to have much useful information.
Thank you Mary. I will certainly take a look at that book.

Jim

Nov 30 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.