Solved

How to create a Sql Server ODBC that is available to network PC's

Posted on 2011-09-23
6
249 Views
Last Modified: 2012-05-12
I have several Access 2007 'front-end' databases that have tables which link to the corresponding 'back-end' Access database.  I am in the process of migrating to SQL SErver 2008 and want to link the tables in the 'front-end' databasses to my new SQL Server.  I did this by creating a System ODBC SQL Server driver, however, the table is only avalable on the machine with the driver ... if I open the database on another machine, the ODBC connection fails.

Is there a way to create a ODBC driver that is avalable to all PC's within our domain?  ... or do I have to install the OBDC driver on every PC?

Thanks
Max
0
Comment
Question by:MaxwellTurner
  • 2
  • 2
  • 2
6 Comments
 
LVL 22

Expert Comment

by:Kelvin Sparks
ID: 36590435
Yes, the drivers must be on every machine. Generally the old SQL Driver is installed with windows - while prefereable, you do not have to use the SQL Native Client 10.0 driver.

Kelvin
0
 
LVL 26

Accepted Solution

by:
Nick67 earned 500 total points
ID: 36590466
The driver must be available on all the machines.
The DSN (data source name, which is how you configured a driver to hook up to an ODBC source) usually is distributed to machines as well.
You can create DSN-less connections.
You can google up lots of good information about doing that.

But the driver--that you gotta have
0
 
LVL 1

Author Comment

by:MaxwellTurner
ID: 36590867
I may have mis-used the word 'driver' ... yes, most of our machines have the drivers ... I was referring to the DSN.  By 'distributed to each machine' I assume you mean must manually be added to each machine, unless I use DSN-less connections.  Never heard of that, but  it sounds like what I need.  I will look into that.

Thanks,
Max
0
6 Surprising Benefits of Threat Intelligence

All sorts of threat intelligence is available on the web. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

 
LVL 26

Expert Comment

by:Nick67
ID: 36590896
You can link tables using code.  That's the heart of a DSN-less connection
0
 
LVL 22

Expert Comment

by:Kelvin Sparks
ID: 36591086
You can also create the dsn in your code.
0
 
LVL 1

Author Comment

by:MaxwellTurner
ID: 36711105
Thanks all,

DSN-less connection is the best solution for me.  All my dbases have a opening form, so it should work great.

Thanks again,

Max
0

Featured Post

Why do Marketing keep bothering you?

Is your marketing department constantly asking for new email signature updates? Are they requesting a different design for every department? Do they need yet another banner added? Don’t let it get you down! There is an easy way to manage all of these requests...

Join & Write a Comment

Suggested Solutions

A simple tool to export all objects of two Access files as text and compare it with Meld, a free diff tool.
Possible fixes for Windows 7 and Windows Server 2008 updating problem. Solutions mentioned are from Microsoft themselves. I started a case with them from our Microsoft Silver Partner option to open a case and get direct support from Microsoft. If s…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
With Microsoft Access, learn how to start a database in different ways and produce different start-up actions allowing you to use a single database to perform multiple tasks. Specify a start-up form through options: Specify an Autoexec macro: Us…

757 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now