Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Database Design / July 2005

Tip: Looking for answers? Try searching our database.

Linking SQL Tables

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
LeAnn - 18 Jul 2005 23:31 GMT
Hi,

I have an Access 97 database that has 3 linked SQL tables.  When I created
the links using my user account, then when I deployed the database, the users
logging on under a generic domain account could not access the tables. The
error is  "ODBC Connection to 'SQL_TableXYZ' failed.".  I linked the tables
through a FileDSN which is using a SQL account to login. I had to recreate
the links under the generic account for the users to access the appropriate
functions.  Now, when I open the database under my account I cannot get
access to them.    

During the "Link Tables" process in Access, there is an "options" button
where the Workstation is listed and of course my workstation is listed if I
try to relink.

How do I avoid this issue?

Thanks
LeAnn
Lynn Trapp - 19 Jul 2005 15:19 GMT
LeAnn,
Have you considered using a Machine Datasource instead of a File Datasource?

Signature

Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

> Hi,
>
[quoted text clipped - 19 lines]
> Thanks
> LeAnn
LeAnn - 20 Jul 2005 01:42 GMT
If I understand it correctly, I think the issue with that is that each
machine will have to have that added to the ODBC Administrator.  I believe we
have had issues with that when a user's computer gets replaced or
re-formatted.  Trying to keep track of which computers need which ODBC
drivers added seemed difficult.  I will look into that though.

Thanks
LeAnn

> LeAnn,
> Have you considered using a Machine Datasource instead of a File Datasource?
[quoted text clipped - 22 lines]
> > Thanks
> > LeAnn
Lynn Trapp - 20 Jul 2005 12:39 GMT
LeAnn,
You are right and, where I work, we make those drivers a part of the
standard image for all PC's. I'm not sure that the Machine Datasource will
solve  your problem, but I have never had much luck going the other way.

Signature

Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

> If I understand it correctly, I think the issue with that is that each
> machine will have to have that added to the ODBC Administrator.  I believe
[quoted text clipped - 38 lines]
>> > Thanks
>> > LeAnn
LeAnn - 21 Jul 2005 19:08 GMT
That would make it easier, unfortunately that is not very practical in my
environment.   Thanks for your input.

> LeAnn,
> You are right and, where I work, we make those drivers a part of the
[quoted text clipped - 43 lines]
> >> > Thanks
> >> > LeAnn
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.