Re: Connect to 4.1 using MyOBDC
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 or888-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]
RE: Connect to 4.1 using MyOBDC
On Friday, September 26, 2003 7:10 AM, Patrick Shoaf wrote: ...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. I'm coming into this discussion late, so I apologize if this is too elementary or has already been discussed...however, we are using MyODBC on windows with MySQL and I've found that I must create my own DSN (via the windows ODBC Admin tool) and actually test the DSN (instantiates the driver?) before I can use the MyODBC driver. -dn -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Connect to 4.1 using MyOBDC
Please tell me it ain't so! My test user is using MyOBDC to connect to our 4.1.0 alpha server. She will be creating some Crystal Reports from the data. Her test DSN fails on an incompatible protocol error with a message that she should upgrade to the newest client. Do I have to download bitkeeper, a C compiler, and learn how to use them to get an OBCD driver that will work with our server? Thanks Randy -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Connect to 4.1 using MyOBDC
I use MyODBC 3.51.06 to connect my VB applications to MySQL and it works. Thanks Emery - Original Message - From: Randy Chrismon [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, September 25, 2003 19:20 Subject: Connect to 4.1 using MyOBDC Please tell me it ain't so! My test user is using MyOBDC to connect to our 4.1.0 alpha server. She will be creating some Crystal Reports from the data. Her test DSN fails on an incompatible protocol error with a message that she should upgrade to the newest client. Do I have to download bitkeeper, a C compiler, and learn how to use them to get an OBCD driver that will work with our server? Thanks Randy -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Connect to 4.1 using MyOBDC
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]
RE: Connect to 4.1 using MyOBDC
I can connect to my v4.1 MySQL server from Crystal Reports v8.5 using MyODBC v3.51. (Via selecting my DSN from the list of ODBC DSNs that Crystal shows me). -Holly -Original Message- From: Randy Chrismon [mailto:[EMAIL PROTECTED] Sent: Thursday, September 25, 2003 10:21 AM To: [EMAIL PROTECTED] Subject: Connect to 4.1 using MyOBDC Please tell me it ain't so! My test user is using MyOBDC to connect to our 4.1.0 alpha server. She will be creating some Crystal Reports from the data. Her test DSN fails on an incompatible protocol error with a message that she should upgrade to the newest client. Do I have to download bitkeeper, a C compiler, and learn how to use them to get an OBCD driver that will work with our server? Thanks Randy -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
