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 / General 1 / March 2005

Tip: Looking for answers? Try searching our database.

How I can attach to tables on another machine on my LAN?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
MLH - 30 Mar 2005 14:03 GMT
I have a DSL line coming in to my home/office into a
4-port router to which 3 windoze boxes and one linux
box are connected. My window$ boxes all see each
other, but I do not have a facility yet for attaching
the linux box's MySQL tables to the MS Access
database across CAT-5, 10BASE-T cabling.

What's the best recommended approach to attaching
to tables on a PC in the next room across my LAN. Of
course, they are MySQL. If they were MS Access, it
would be easy.
Alan Webb - 30 Mar 2005 15:22 GMT
MLH,
ODBC Driver?  The location on the LAN shouldn't matter.  The type of network
cable or connection speed shouldn't be an issue on a lightly loaded network.
Assuming there isn't a huge amount of transaction volume on this database
even a crappy 802.11b wireless connection would work.  Access is pretty good
at connecting to and using data from a whole lot of sources, MySQL among
them.  I believe it's a matter of finding, installing and configuring an
ODBC driver.  But brighter lights than me (Hi, Larry) can help you there.

Signature

Alan Webb
knoNOgeek@SPAMhotmail.com
"It's not IT, it's IS

>I have a DSL line coming in to my home/office into a
> 4-port router to which 3 windoze boxes and one linux
[quoted text clipped - 7 lines]
> course, they are MySQL. If they were MS Access, it
> would be easy.
dedejavu@hotmail.com - 30 Mar 2005 18:10 GMT
Alan is right,
Download the windows myodbc drivers from mysql.com and you should have
no trouble connecting using access.
To link them you can setup a dsn or use dao's tabledef.connect property
and with an ado connection string.
HTH
Pachydermitis
MLH - 31 Mar 2005 14:05 GMT
I have attached to MySQL servers in other states and other countries
on the other side of my router. But when I use the MySQL ODBC driver
3.51 to connect on my own LAN, the driver tells me it cannot make the
connection. Here are the ODBC driver connection parms:

Data Source Name: (free field - name my "my linux box" will do nicely)
Host/Server Name (or IP) - something like MSQLUserName@ServerName.net
    has worked fine for me in the past. Now I'm trying 192.168.1.106.
Database Name - whatever, mysqldb works fine, any valid db
User - root
Password - myrootpass
Port - 3306 has worked fine 4 me N the past. Dunno whether 2 use now
SQL Command On Connect - haven't ever put anything here

Perhaps there is some configuration in mysql user privilege for the
mysqluser "root" that would prevent him from logging from a remote PC
to the mysql server???

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

>MLH,
>ODBC Driver?  The location on the LAN shouldn't matter.  The type of network
[quoted text clipped - 4 lines]
>them.  I believe it's a matter of finding, installing and configuring an
>ODBC driver.  But brighter lights than me (Hi, Larry) can help you there.
Alan Webb - 31 Mar 2005 14:50 GMT
MLH,
All the Unix guys on the 'Net are collectively groaning and shouting.  User
name of "root"?  Shame on you.  Set up an account on the Linux box
specifically for your application that has appropriate priviledges.  Try
connecting with that.

Signature

Alan Webb
knoNOgeek@SPAMhotmail.com
"It's not IT, it's IS

>I have attached to MySQL servers in other states and other countries
> on the other side of my router. But when I use the MySQL ODBC driver
[quoted text clipped - 27 lines]
>>them.  I believe it's a matter of finding, installing and configuring an
>>ODBC driver.  But brighter lights than me (Hi, Larry) can help you there.
MLH - 31 Mar 2005 17:40 GMT
Hey, I hear you. Actually, MySQL user ID's are completely unique,
separate and have nothing to do with Linux OS login's. MySQL
automatically sets up two root accounts. Neither of these have
anything at all to do with the Linux OS root login account.

anonymous may just turn out to be the answer. BTW, I have no
linux login ID named anonymous. Will let you know how it pans out.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

>MLH,
>All the Unix guys on the 'Net are collectively groaning and shouting.  User
>name of "root"?  Shame on you.  Set up an account on the Linux box
>specifically for your application that has appropriate priviledges.  Try
>connecting with that.
Alan Webb - 31 Mar 2005 19:54 GMT
MLH,
You sound like a better DBA than this, but pretty much any DBA worth is
title knows the default accounts that get set up at install time so that the
DBA can go in and configure the DBMS instance.  Hackers know these accounts
as well.  It shouldn't work to try one of the install acounts but boy, if it
does, it makes stealing data such an easy task.  I ranted because it's
really lame of a DBA to leave those accounts unchanged once he's made a
first pass at setting up appropriate admin accounts.  But I digress . . .
my best guess is that this is a login issue and not so much a network
connectivity or ODBC issue.
Signature

Alan Webb
knoNOgeek@SPAMhotmail.com
"It's not IT, it's IS

> Hey, I hear you. Actually, MySQL user ID's are completely unique,
> separate and have nothing to do with Linux OS login's. MySQL
[quoted text clipped - 11 lines]
>>specifically for your application that has appropriate priviledges.  Try
>>connecting with that.
 
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.