I am having a very big problem with the way Fox is interacting with the
MySQL odbc driver.  Below is the connection string that I am using to
connect to my  db server.  There are a couple of problems that I am running
into.
1.      In a sql pass through any of the varchars on the server are coming
through as a char.  That is not a problem the problem comes when I connect
the cursor to the backend server make a couple of changes and push updates.
All of the character fields get padded out with spaces.  That is inflating
the db and causing problems with indexes and locate statements.
2.      If I open up an actual remote view and not use sqlexec() and not do
anything with the view for an amount of time then try to close the view I
get a fatal odbc error.  SQL Server has gone away error number 2006.  

I have looked on line for some resolution but have not found any.  
Server version: 5.0.32
Driver version: 3.51.15.00 and 3.51.12.00  I have the same problems with
both versions.

Is there any way to get the padding to sop and the disconnect to stop as
well?????

DATABASE=atto;DRIVER={MySQL ODBC 3.51
Driver};OPTION=2057;PWD=*****;PORT=3306;SERVER=*******;UID=*******



No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.472 / Virus Database: 269.8.6/828 - Release Date: 6/1/2007
11:22 AM
 


--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to