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

Linking to SQL Server 2000

P: n/a
I have an Access 2000 front end that I wish to work with a SQL Server
2000 database by means of Linked tables.
Do I have to use an ODBC connection to SQL Server?
It seems to be the only option offered in the table linking dialog.
Is there a more direct connection with OLE_DB?

John South
Pangbourne UK
Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
ADP

"John South" <js****@cix.co.uk> wrote in message
news:d2**************************@posting.google.c om...
I have an Access 2000 front end that I wish to work with a SQL Server
2000 database by means of Linked tables.
Do I have to use an ODBC connection to SQL Server?
It seems to be the only option offered in the table linking dialog.
Is there a more direct connection with OLE_DB?

John South
Pangbourne UK

Nov 12 '05 #2

P: n/a
On 16 Sep 2003 09:36:26 -0700 in comp.databases.ms-access,
js****@cix.co.uk (John South) wrote:
I have an Access 2000 front end that I wish to work with a SQL Server
2000 database by means of Linked tables.
Do I have to use an ODBC connection to SQL Server?
It seems to be the only option offered in the table linking dialog.
Is there a more direct connection with OLE_DB?


For linking tables, ODBC is the way, nowt wrong with it, you can
bypass jet using pass-through queries, etc the only stumbling block
will be on low bandwidth connections where you discover that Access
likes to use a little more bandwidth than you anticipated, especially
re-linking over a slow link, on one site I worked on everything was
connected by Microwave or Breezecom radio links, re-linking 250 tables
over that lot used to take about 20 minutes, some forms took more than
a second or two to open but once in it was pretty fast. On a LAN
you'll have no problems except with exceptionally inefficient queries
either by you or by the way Jet interprets them, redesign it as a view
on the server... problem solved.

For OLEDB linked tables you need a ADP, not sure if Access 2000
supports those, long time since I looked at that version. The downside
to ADPs from what I can see is no local tables, queries e.g. you can
get away with VBA functions in queries, not with an ADP as they're
views on the server.

--
A)bort, R)etry, I)nfluence with large hammer.

(replace sithlord with trevor for email)
Nov 12 '05 #3

P: n/a
I found "Microsoft Access Developer's Guide to SQL Server" by Mary Chipman
and Andy Baron well worth the price.

HTH

Ernie Scofield
I have an Access 2000 front end that I wish to work with a SQL Server

Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.