Bob Alston wrote:
With all the recent discussions on ADPs and their lack of success, can
someone point me to some GOOD reading on what is required to link MDBs
to SQL Databases / Microsoft SQL Server 2000 Desktop Engine.
Also are their any good, concise summaries of key differences that
someone with Access/Jet experience would need to understand?
In Control Panel you set up a DSN that points to the SQL Server instance and
database that you want to use. Then in Access...
File - Get External Data - Link Tables
Choose ODBC Data Source as the type, choose the DSN you created in step one, and
when the list of tables is displayed select those you want and press [OK].
Once you have links created you can largely work with them in the same manner as
you would Access tables. Now...doing this exclusively might not be the
"optimum" way to use a SQL Server database from a client, but it will work to
get you started. From there you simply find the places that need performance
enhancement and that is where you spend your time doing things differently.
A lot of the "re-design" that moving to client-server involves comes from people
who didn't have a very good multi-user (networked) design in the first place.
If your "all Access" application is using all of the best practices for
efficient data handling then it might need very little re-work when you move the
back end to SQL Server.
The problem comes from instances where Access allows you to get away with some
pretty awful design habits and then when you move to a server back end it
performs like crap. The notion that all your DAO has to be re-written and all
queries changed into Stored Procedures and Views is simply wrong. Some of them
will, yes. Many others will be fine as plain old Access queries.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com