I believe the problem is in the ODBC drivers on MS Winx platforms. I have no problems accessing MySQL from MySQL Control Center or from perl or other programs NOT using ODBC. I have a MS FoxPro application using ODBC to connect to MS SQL Server via TCP/IP and MS FoxPro has problems connecting sometime to MS SQL. Given that problem, and my success accessing MySQL from any place with a natural (not ODBC) driver, I would look to ODBC first the MySQL second.

At 01:57 PM 9/25/2003, Randy Chrismon wrote:
Seems to be a problem with the fact that the server is on a Linux
box.
I was having this problem connecting the mysql command environment to
the linux server until I added -protocol=TCP to the login statement.
Or maybe it's just that we use a TCP/IP network (doesn't everybody?).
Anyway, my test user is using Win2K, accessing the MySQL server which
resides on a Redhat 9 linux box. We are on the same network domain
inside the firewall. Essentially, I believe I need some way to tell
the ODBC driver (and also the mysql command center and the command
line) that the protcol is TCP. Is their an environment variable that
would do this? This is starting to make me look bad...
Thanks.
Randy

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]


Patrick J. Shoaf, Systems Engineer
<mailto:[EMAIL PROTECTED]>[EMAIL PROTECTED]

Midmon Internet Services, LLC
100 Third Street
Charleroi, PA 15022
http://www.midmon.com
Phone: 724-483-2400 ext. 105
 or    888-638-6963
Fax:   724-489-4386



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to