Linking SQL Server to Access 2000

E

Ed Warren

My applications have been divided into a front end and back end in Access
Now it is time to move the data to SQL server.

I have 'upsized' the data (backend) files with no problems.

Now I need to "link" the application files to the SQL server data files.

I can figure out how to link via ODBC.

Is there a better way? Like doing it via ADO (ADO.net)??


Thanks

Ed Warren
 
A

Albert D. Kallal

My applications have been divided into a front end and back end in Access
Now it is time to move the data to SQL server.

I have 'upsized' the data (backend) files with no problems.

Now I need to "link" the application files to the SQL server data files.

I can figure out how to link via ODBC.

Is there a better way? Like doing it via ADO (ADO.net)??

The linked tables will not perform any better via odbc, or ado anyway. (but,
the answer is no, not really any better way).

You can create in ms-access a adp project, and that means all data
connections are a OLEdb (ado) native connection to sql server. For building
queries and like, these ADO projects are better since you don't have to
worry about doing stupid things that can hurt performance like you can with
linked odbc tables. So, while linked tables can perform very well, it is the
design of the application that will effect performance most.
 
E

Ed Warren

Thanks, I've looked at the ADP, and may go that way, but wanted to limit the
recoding required to get all the queries to work properly.

When I looked at how Access does this in the 'Upsizing wizard', I see they
use an ODBC connection, so I'm probably stuck there or going the ADP route.

Again Thanks for the response.

Ed Warren
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top